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.
git clone --depth 1 https://github.com/Himanshu507/cgconeWrote 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/commands/himanshu507/cgcone/explain)<a href="https://agentmods.dev/commands/himanshu507/cgcone/explain"><img src="https://agentmods.dev/badge/commands/himanshu507/cgcone/explain/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/commands/himanshu507/cgcone/explain"><img src="https://agentmods.dev/badge/commands/himanshu507/cgcone/explain.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.00015 | $0.00073 |
| Opus 5.5 | $0.00006 | $0.00029 |
| Sonnet 5.5 | $0.00003 | $0.00015 |
| Haiku 4.5 | $0.00002 | $0.00007 |
Grade A, and why
explain 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.
What it actually says
Provide a clear, concise explanation with practical examples. Adapt the technical depth to the apparent expertise level of the question. Use analogies where helpful.
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 · 11 lines · 15 tokens per session scan A e379e7e911c3
explain is a command published in the GitHub repository Himanshu507/cgcone (9 stars, last pushed yesterday), licensed MIT. It adds 15 tokens to every session and 73 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 commands, from other repositories
certificado
Gera um certificado fictício em markdown com nome do usuário e trilha concluída.
desafio
Gera um desafio de código aleatório para a tecnologia e nível escolhidos.
trilha
Exibe o plano de estudos de uma trilha DIO pela tecnologia.
complete
Review implementation evidence and plan the spec completion transaction.
speckit.gym.drop
Record a drop card from a mis-fire. A mis-fire is not a mistake to punish — it is a discovery to keep. Drop cards capture what was done, what was expected, and what happened, persisted to the configured redundant stores (default /drops/ plus the extension's append-only .drop-ledger.md).
learn
Start learning a new topic — asks clarifying questions, researches resources, and creates a structured learning plan.