Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/bnet47/codexiconnpx agentmods add skills/bnet47/codexicon/quickWrote 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/bnet47/codexicon/quick)<a href="https://agentmods.dev/skills/bnet47/codexicon/quick"><img src="https://agentmods.dev/badge/skills/bnet47/codexicon/quick/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/bnet47/codexicon/quick"><img src="https://agentmods.dev/badge/skills/bnet47/codexicon/quick.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.00023 | $0.00535 |
| Opus 5.5 | $0.00009 | $0.00214 |
| Sonnet 5.5 | $0.00005 | $0.00107 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
quick 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick change
Use this path only when the desired behavior and implementation approach are clear.
Gate
Inspect the target and confirm:
- the change is coherent and tightly coupled;
- no new dependency, migration, or expensive-to-reverse choice is required;
- acceptance can be verified with existing commands or a small focused test.
Before editing, trace the requested code/configuration/document change to an existing SPEC.md requirement and interface, and to an existing TASKS.md task when a register already covers the work. If no register is needed, a current authorized request may make one minimal append-only amendment to root SPEC.md; do not invent a task ID. If the work needs a new queued task or multiple steps, route to $write-plan and $autonomous-build instead. Pure explanations and read-only reviews are exempt from this gate and from code-generation ceremonies.
If not, route to $brainstorm, $investigate, $spec, or $write-plan as appropriate.
Execute
- State the trace (
T-* -> R-* -> I-*, orR-* -> I-*when no register is needed) and intended file scope in one sentence. - Preserve unrelated edits and implement the smallest complete solution.
- Add or update focused tests for changed behavior when applicable.
- Run the narrowest relevant check. For code, configuration, generated artifacts, or shipping readiness, also run:
./scripts/lint.sh
./scripts/test.sh
For documentation-only changes, run the applicable documentation or structural check and explicitly report why the broader test suite was not needed.
- Review the diff for scope, acceptance coverage, and accidental generated files.
- Report the outcome and verification evidence.
Use the shared task states TODO, ACTIVE, BLOCKED, and DONE and queue outcomes READY, RESUME_ACTIVE, BLOCKED, COMPLETE, and INVALID when a register is involved. Build has one writer in the shared checkout: the primary agent by default. An explicitly chosen implementer may write one bounded task sequentially; the primary agent re-reads the changed paths and owns integration and final verification. Never run concurrent writers.
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 Changed 652737c85fa3
- 1mo ago Changed · +4 lines c7fdbe1864d0
- 1mo ago First seen · 39 lines · 23 tokens per session scan A 789b974d9f63
quick is a skill published in the GitHub repository bnet47/codexicon (5 stars, last pushed 20d ago), licensed MIT. It adds 23 tokens to every session and 535 once invoked, about $0.0001 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
agent-harness-fault-injection
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.
make_plan
For external plan request scenarios, guides the Agent to request a clear, actionable, step-by-step plan from a stronger Agent via listagents and chatwithagent, emphasizing that the plan is executed by the requester, not by the consulted Agent.
requirements-writer
Use when converting PM intake into a slice SPEC.md with observable acceptance outcomes, explicit scope, and advisory sibling build dependencies.
orchestration-team
Use when coordinating assignments, selected review boundaries, or blocked work across a rig.
oversight-team
Use when you are a seat on the oversight pod (a standing monitor-mode rig that keeps OTHER rigs healthy), configuring or running the drift detectors, or choosing whether to intervene vs escalate. Covers the pull-not-poll posture, the v0 detectors (premature-park, process-drift, off-task, token-burn), the intervention…
oma-scholar
Search academic literature and generate, validate, or compare Knows paper sidecars. Use for claim/evidence analysis and literature synthesis.