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 agentmods add commands/icloudza/algokiller-plugin/statusgit clone --depth 1 https://github.com/icloudza/algokiller-pluginWhat 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 | $0.00023 | $0.00296 |
| Opus 5 | $0.00012 | $0.00148 |
| Sonnet 5 | $0.00005 | $0.00059 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
status 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 yesterday.
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
Report the current algokiller session state in this exact structure:
- Trace binding — call
bind_traceis required first. If no trace is bound yet, say so and stop. - Output directory — show the
output_dir_resolvedandoutput_dir_sourcefrom the latestbind_traceresponse (you should have it in context; if not, callbind_traceagain to refresh). - Hypothesis ledger — call
hypothesis_listand present:- count of
concluded/active/abandoned/archivedhypotheses - one-line summary of each concluded hypothesis (id, final_confidence, statement)
- any
activehypothesis withconfidence: highthat hasn't been concluded (these are dangerous open threads)
- count of
- Artifacts written this session — call
list_artifactsand list each file by name + size; group by extension (.pyvs.md). - Recommendations — single short paragraph: are there active hypotheses that should be concluded? unreferenced concluded ones that need archive? falsification gaps? Suggest the next concrete action.
Keep the whole report under 500 words. Don't dump raw JSON; format as a compact human-readable digest.
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.
- yesterday First seen · 17 lines · 23 tokens per session scan A f0d622ebf69c
status is a command published in the GitHub repository icloudza/algokiller-plugin (77 stars, last pushed 3mo ago), licensed MIT. It adds 23 tokens to every session and 296 once invoked, about $0.0001 per session on Opus 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-30.
Other commands, from other repositories
workflow-foundation-sprint
Run the Foundation Sprint workflow (2-day strategic-alignment arc producing a Founding Hypothesis).
workflow-foundation-to-design
Run the end-to-end Foundation Sprint + Design Sprint workflow with narrative handoff.
workflow-technical-discovery
Run the Technical Discovery workflow (spike -> ADR -> design rationale).
memcord-save-progress
Auto-summarize and save conversation progress.
memcord-unbind
Remove .memcord binding from a project directory.
enrich
Enrich project memory by mining 100 recently merged PRs: extracts decisions, conventions, gotchas, and architectural facts from PR discussions, review comments, and PR bodies.