Generated source template injection
- Finding
- User-controlled placeholder is embedded directly into generated source code.
Security checks across static analysis, malware telemetry, and agentic risk
The skill appears aligned with Higress gateway administration, but it relies on undeclared admin credentials/session cookies and can make persistent gateway changes, so it should be reviewed before use.
Only install this if you intend to let the agent administer your local Higress gateway. Confirm the admin cookie and password handling, review every create/update/delete request before it runs, and avoid using it for production routes or provider credentials without a rollback plan.
VirusTotal findings are pending for this skill version.
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
An agent using this skill can authenticate to the local Higress Console as an administrator and change gateway configuration.
The skill tells the agent to use Higress admin credentials and a session cookie, but the registry metadata says there are no required environment variables or primary credential. That under-discloses privileged account access.
HICLAW_ADMIN_PASSWORD # Admin password for Higress Console
HIGRESS_COOKIE_FILE # Path to session cookie file
...
Use it with `curl -b "${HIGRESS_COOKIE_FILE}"`.Declare the required credentials and environment variables in metadata, document the exact privilege scope, and require explicit user approval before any mutating operation.
A mistaken or over-broad command could remove consumers, rotate credentials, or break AI routing.
The skill documents direct administrative API calls that update and delete gateway objects. These are purpose-aligned, but they are high-impact operations.
curl -X PUT http://127.0.0.1:8001/v1/ai/routes/default-ai-route ... -d "$UPDATED"
...
curl -X DELETE http://127.0.0.1:8001/v1/consumers/worker-alice -b "${HIGRESS_COOKIE_FILE}"Use this skill only for explicit user-requested changes, review the target object and payload before execution, and keep a rollback or backup plan for route and credential changes.
Incorrect route changes could affect many or all AI model requests passing through the gateway.
The skill acknowledges that route changes can affect all model traffic through the gateway, so a bad update could have broad downstream impact.
The system initializes with a `default-ai-route` that has no `modelPredicates` — all model requests go through it.
Test route changes narrowly, prefer explicit model predicates, and confirm expected traffic impact before updating default routes.