Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add echoomegaprime/echo-qcoder --skill qcoder-authorized-securitygit clone --depth 1 https://github.com/echoomegaprime/echo-qcoderWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/echoomegaprime/echo-qcoder/qcoder-authorized-security)<a href="https://agentmods.dev/skills/echoomegaprime/echo-qcoder/qcoder-authorized-security"><img src="https://agentmods.dev/badge/skills/echoomegaprime/echo-qcoder/qcoder-authorized-security/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/echoomegaprime/echo-qcoder/qcoder-authorized-security"><img src="https://agentmods.dev/badge/skills/echoomegaprime/echo-qcoder/qcoder-authorized-security.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00079 | $0.00558 |
| Opus 5.5 | $0.00032 | $0.00223 |
| Sonnet 5.5 | $0.00016 | $0.00112 |
| Haiku 4.5 | $0.00008 | $0.00056 |
Grade A, and why
qcoder-authorized-security scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QCoder Authorized Security
Expected input
Identify the exact target, owner or authorization basis, allowed techniques, exclusions, time window, and desired evidence. Treat a color label as an operating perspective, not permission to expand scope.
Required sequence
- Read the ECHO pentester role, security modules, target repository instructions, and current scope record.
- Switch the durable SOL mission to
pentesterbefore active testing and read every returned context packet path. - Discover the current scoped security capabilities through
echo.caps.searchorecho.caps.list; never guess a moving command contract. - Validate scope before sending traffic. Begin with passive evidence, then perform the minimum active validation required by the objective.
- Route active operations through the signed and audited ECHO Prometheus/CRUCIBLE control plane. Supply exact confirmation tokens when a capability requires them.
- Preserve evidence, timestamps, target identity, tool result, and rollback or cleanup state. Separate observed facts from hypotheses.
- Remediate only when requested, then retest the immutable candidate and record residual risk.
Color routing
- Blue: detection, hardening, containment, recovery, and control validation.
- Red: scoped adversarial validation with explicit target and stop conditions.
- Purple: paired attack and detection evidence with control improvement.
- Orange, yellow, and green: use the definitions in the current ECHO pentester context packet; do not invent a target, identity, social pretext, or public action.
Third-party frameworks
CAI, PentestGPT, and Strix are research candidates, not automatic execution paths. Before adoption, pin a revision, review license and telemetry, inspect containers and tool permissions, run dependency and secret scans, and expose only bounded adapters behind the ECHO scope/confirmation layer. CAI requires separate commercial permission for professional or production use.
Stop conditions
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 40 lines · 79 tokens per session scan A 4743cd03c267
qcoder-authorized-security is a skill published in the GitHub repository echoomegaprime/echo-qcoder (0 stars, last pushed yesterday), licensed MIT. It adds 79 tokens to every session and 558 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.