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/zahardev/aicontextWrote 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/zahardev/aicontext/close-task)<a href="https://agentmods.dev/commands/zahardev/aicontext/close-task"><img src="https://agentmods.dev/badge/commands/zahardev/aicontext/close-task/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/zahardev/aicontext/close-task"><img src="https://agentmods.dev/badge/commands/zahardev/aicontext/close-task.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.00013 | $0.00037 |
| Opus 5.5 | $0.00005 | $0.00015 |
| Sonnet 5.5 | $0.00003 | $0.00007 |
| Haiku 4.5 | $0.00001 | $0.00004 |
Grade A, and why
close-task 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 26d 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
Read and follow .aicontext/prompts/close-task.md
$ARGUMENTS
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.
- 26d ago First seen · 8 lines · 13 tokens per session scan A a6f7ac5d0d7b
close-task is a command published in the GitHub repository zahardev/aicontext (2 stars, last pushed 17d ago), licensed MIT. It adds 13 tokens to every session and 37 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-09-20.
Other commands, from other repositories
feature-config
Phase 0 of develop: Configuration wizard, escape hatches, preferences, continuation detection.
polish-repo-community
Phase 3 of polish-repo: Community infrastructure, issue templates, roadmap, contributor experience, and signs of life.
create-issue
Create a GitHub issue with proper template discovery and population.
estimate-buffer
Phases 6-7 of estimating-tickets. PERT three-point estimation per ticket + Brooks's Law resource scaling.
estimate-scope
Phase 1-3 of estimating-tickets. Ingest the test card, validate external-domain constraints, build a structural repo map, decompose into tickets tagged by repo.
polish-repo-audit
Phases 0-1 of polish-repo: Reconnaissance gathering and audit scorecard generation.