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/VoxTechnologies/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/voxtechnologies/anty-framework/loop)<a href="https://agentmods.dev/commands/voxtechnologies/anty-framework/loop"><img src="https://agentmods.dev/badge/commands/voxtechnologies/anty-framework/loop/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/voxtechnologies/anty-framework/loop"><img src="https://agentmods.dev/badge/commands/voxtechnologies/anty-framework/loop.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.00008 | $0.00819 |
| Opus 5.5 | $0.00003 | $0.00328 |
| Sonnet 5.5 | $0.00002 | $0.00164 |
| Haiku 4.5 | $0.00001 | $0.00082 |
Grade A, and why
loop 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- loop — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/anty:loop — Persistent Operation
Trigger
User runs /anty:loop [interval]
Arguments
/anty:loop 30m— Run scan every 30 minutes/anty:loop 1h— Run scan every hour/anty:loop 2h— Run scan every 2 hours/anty:loop stop— Stop the running loop
Behavior
Establish a persistent scan loop that repeatedly executes /anty:scan at the specified interval. Uses the loop skill pattern for continuous operation within a Claude Code session.
Starting the Loop
- Parse the interval argument (e.g.,
30m,1h,2h) - Validate interval is between 10m and 24h
- Display confirmation:
Anty loop started. Interval: [interval] Next scan: [timestamp] Use /anty:loop stop to end. - Begin the loop cycle
Loop Cycle
Each iteration:
- Read state: Load all
.anty/files to get current state - Execute scan: Run the full
/anty:scan10-point analysis - Evaluate findings:
- If issues found with severity >= warning:
- Generate recovery Action proposals
- Notify user with a summary of findings
- If no issues: log clean scan silently
- If issues found with severity >= warning:
- Save results: Write scan results to
.anty/history/scans/[date].yaml - Append to scratchpad: Add scan summary to
.anty/scratchpad.md - Wait: Sleep for the specified interval
- Repeat: Go to step 1
Notification Thresholds
Only notify the user (interrupt their work) when:
- Buffer zone transitions (GREEN->YELLOW, YELLOW->RED)
- Pipeline deal stalls detected (2x average dwell time)
- Failure pattern detected (3+ consecutive failures)
- Anti-pattern detected
- Growth rate drops below 5%/week
- Environmental disruption risk detected
- Oscillation pattern detected
For non-critical findings, accumulate and report at next user interaction.
Notification Format
----------------------------------------------------
ANTY LOOP — [timestamp]
----------------------------------------------------
[severity] [check name]: [one-line summary]
[n] recovery proposals generated.
Run /anty:actions to review.
----------------------------------------------------
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.
- 1mo ago First seen · 109 lines · 8 tokens per session scan A 552f918751ba
loop is a command published in the GitHub repository VoxTechnologies/anty-framework (6 stars, last pushed 6mo ago), licensed MIT. It adds 8 tokens to every session and 819 once invoked, about $0.0000 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-08-31.
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.