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/ingramradical235/anty-framework/statusgit clone --depth 1 https://github.com/Ingramradical235/anty-frameworkWrote 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/ingramradical235/anty-framework/status)<a href="https://agentmods.dev/commands/ingramradical235/anty-framework/status"><img src="https://agentmods.dev/badge/commands/ingramradical235/anty-framework/status.svg" alt="Measured on agentmods" 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 | $0.00008 | $0.00827 |
| Opus 5 | $0.00004 | $0.00413 |
| Sonnet 5 | $0.00002 | $0.00165 |
| Haiku 4.5 | $0.00001 | $0.00083 |
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 4d 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.
This is a copy
100% identical to status — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/anty:status — CLI Dashboard
Trigger
User runs /anty:status
Behavior
Read ALL files in the .anty/ directory tree to gather current state, then display a formatted ASCII dashboard.
Steps
-
Read all .anty/ files:
.anty/goals/*.yaml— Goal definitions, progress, buffer.anty/drivers/*.yaml— Driver definitions, impact_weight, metrics.anty/actions/*.yaml— Action statuses.anty/pipeline/config.yaml— Pipeline step definitions.anty/pipeline/deals/*.yaml— Active deals.anty/scratchpad.md— Working memory entries.anty/config.yaml— Configuration.anty/history/scans/— Last scan timestamp
-
Display formatted dashboard:
====================================================
ANTY STATUS DASHBOARD
====================================================
Goal: [goal name] ([timeframe])
Progress: [progress bar] [current]/[target] ([%])
Buffer: [zone] ([consumption]% consumed)
Growth: [weekly rate]%/week (YC: [assessment])
----------------------------------------------------
CRUX DRIVER
----------------------------------------------------
Constraint: [driver name]
Impact Weight: [weight]%
----------------------------------------------------
WIP STATUS
----------------------------------------------------
Constraint WIP: [n]/[limit]
Non-constraint WIP: [n]
Total WIP: [total]/[max]
----------------------------------------------------
DRIVERS (sorted by impact_weight)
----------------------------------------------------
[star] [name] wt:[weight]% metric:[value]% [CONSTRAINT]
[name] wt:[weight]% metric:[value]%
[name] wt:[weight]% metric:[value]%
----------------------------------------------------
PIPELINE
----------------------------------------------------
Active Deals: [n] | Weighted Value: $[value]
Bottleneck: Step [n] ([name])
----------------------------------------------------
ACTIONS
----------------------------------------------------
Pending: [n] actions awaiting approval
Run /anty:actions to review
----------------------------------------------------
SCRATCHPAD
----------------------------------------------------
[SUCCESS]: [n] | [FAILURE]: [n]
[PATTERN]: [n] | [INSIGHT]: [n]
Last scan: [timestamp]
====================================================
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.
- 4d ago First seen · 111 lines · 8 tokens per session scan A e2e4c662e3da
status is a command published in the GitHub repository Ingramradical235/anty-framework (1 stars, last pushed 2d ago), licensed MIT. It adds 8 tokens to every session and 827 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to status, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
scan
/anty:scan — Analysis Cycle (10-Point).
pipeline
/anty:pipeline — Sales Pipeline Management.
status
/anty:status — CLI Dashboard.
task
Guided task intake — interviews the user, writes a plan following TASKINTAKE.md format, validates structure, then submits to the autonomous task executor.
prime-pm-role
Prime the PM (project manager) persona for the headless session runner. Receives the user message as $ARGUMENTS.
onboard
/anty:onboard — QUEST-Based Conversational Interview.