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/actionsgit 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/actions)<a href="https://agentmods.dev/commands/ingramradical235/anty-framework/actions"><img src="https://agentmods.dev/badge/commands/ingramradical235/anty-framework/actions.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.00016 | $0.02002 |
| Opus 5 | $0.00008 | $0.01001 |
| Sonnet 5 | $0.00003 | $0.00400 |
| Haiku 4.5 | $0.00002 | $0.00200 |
Grade A, and why
actions 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 5d 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 actions — 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/anty:actions — 3-Option Choice Approval with Nudge Architecture
Purpose
Present pending action proposals as structured 3-option choices, using behavioral nudge architecture to support high-quality decisions. Record choices to build the founder's preference profile over time.
Prerequisites
.anty/business-context.yamlmust exist. If not: "Run/anty:onboardfirst.".anty/actions/directory must contain at least one action file withstatus: proposed. If no pending actions: "No pending actions to review. Run/anty:planto generate strategy and action proposals."
Step 1: Load Context
Read the following files to build decision context:
.anty/business-context.yaml(founder's business context).anty/learning/preferences.yaml(if exists — accumulated preference distributions).anty/learning/choice-history.yaml(if exists — past choices).anty/learning/performance-labels.yaml(if exists — past action outcomes)- All files in
.anty/actions/withstatus: proposed
Step 2: For Each Pending Action
Process each proposed action one at a time. Never present multiple action decisions simultaneously.
2a: RECAP (Relevant Context and Priming)
Before presenting options, surface the founder's own data. This is NOT the agent's opinion — it is a mirror of what the founder has already said and what the data shows.
Format:
--- Your Context ---
Business: [product description from business-context]
Current traction: [key metrics from business-context or recent scans]
Strategic mode: [effectuation/causation/hybrid]
Distribution tier: [tier from business-context]
Pain classification: [painkiller/vitamin]
[Any relevant recent performance data from scans or action outcomes]
---
2b: Present 3 Options
Each option must include:
Option A: [Title]
What: [Clear description of the action]
Expected timeline: [How long this will take]
Expected results: [Quantified outcome — be specific]
Cost: [Money, time, effort required]
Time required: [Hours per week or total hours]
First step: [Channel factor — the concrete, immediate next action]
Option B: [Title]
[Same structure]
Option C: [Title]
[Same structure]
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.
- 5d ago First seen · 213 lines · 16 tokens per session scan A 8e4009ea13ba
actions is a command published in the GitHub repository Ingramradical235/anty-framework (1 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 2,002 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to actions, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
plan
/anty:plan — Strategy Kernel Generation.
onboard
/anty:onboard — QUEST-Based Conversational Interview.
actions
/anty:actions — 3-Option Choice Approval with Nudge Architecture.
review
/anty:review — 5-Question Review Engine.
scan
/anty:scan — Analysis Cycle (10-Point).
quickstart
/anty:quickstart — 5-Minute Quick Onboarding to First Action.