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/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/pipeline)<a href="https://agentmods.dev/commands/ingramradical235/anty-framework/pipeline"><img src="https://agentmods.dev/badge/commands/ingramradical235/anty-framework/pipeline.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.1 | $0.00009 | $0.01063 |
| Opus 5 | $0.00005 | $0.00531 |
| Sonnet 5 | $0.00002 | $0.00213 |
| Haiku 4.5 | $0.00001 | $0.00106 |
Grade A, and why
pipeline 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 7d 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 pipeline — 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/anty:pipeline — Sales Pipeline Management
Trigger
User runs /anty:pipeline optionally followed by a subcommand.
Behavior
Manage the sales pipeline stored in .anty/pipeline/. Display pipeline board, add/update deals, detect bottlenecks, and track flow.
Default View (no subcommand)
Display the pipeline as an ASCII table with steps as columns and deals as rows:
====================================================
PIPELINE BOARD
====================================================
Step 1 Step 2 Step 3 Step 4 Step 5
Prospect Qualify Demo Proposal Close
---------- ---------- ---------- ---------- ----------
Acme Corp BigCo Inc StartupX
SmallBiz MedCorp
TechFirm
Utilization: 60% 40% 20% 0% 0%
Deals: 6 active | Weighted: $127K | Avg cycle: 18 days
====================================================
BBS SUMMARY
----------------------------------------------------
Opening pipeline: $200K (6 deals)
+ New this period: $50K (2 deals)
- Closed won: $30K (1 deal)
- Closed lost: $15K (1 deal)
= Closing pipeline: $205K (6 deals)
====================================================
Subcommands
/anty:pipeline add
Add a new deal to the pipeline.
- Ask for deal information:
- Company name
- Contact name and role
- Estimated deal value
- Starting step (default: Step 1)
- Notes
- Generate deal ID (deal-NNN, sequential)
- Save to
.anty/pipeline/deals/deal-NNN.yaml
Deal YAML structure:
id: deal-001
company: "Acme Corp"
contact: "Jane Smith, CTO"
value: 25000
step: 1
step_name: "Prospect"
probability: 0.10
status: active
created_at: 2026-03-20T10:00:00Z
updated_at: 2026-03-20T10:00:00Z
dwell_days: 0
notes: "Met at conference"
history:
- step: 1
entered_at: 2026-03-20T10:00:00Z
/anty:pipeline update [deal-id]
Update deal details (value, contact, notes, status).
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.
- 7d ago First seen · 139 lines · 9 tokens per session scan A 5dfc9f427b96
pipeline is a command published in the GitHub repository Ingramradical235/anty-framework (1 stars, last pushed today), licensed MIT. It adds 9 tokens to every session and 1,063 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 pipeline, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
onboard
/anty:onboard — QUEST-Based Conversational Interview.
plan
/anty:plan — Strategy Kernel Generation.
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.