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/akaszubski/autonomous-dev/setupgit clone --depth 1 https://github.com/akaszubski/autonomous-devWhat 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.00017 | $0.03766 |
| Opus 5 | $0.00009 | $0.01883 |
| Sonnet 5 | $0.00003 | $0.00753 |
| Haiku 4.5 | $0.00002 | $0.00377 |
Grade C, and why
setup scanned grade C with 3 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
**Why**: Per-repo `.mcp.json` is the recommended default. MCP servers configured globally in `~/.claude/settings.json` mcpServers inject tool definitions into every prompt — even when irrelevant — costing 5-10K tokens pe Reads MCP configurationmediumAgent snooping
mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.
**Why**: Per-repo `.mcp.json` is the recommended default. MCP servers configured globally in `~/.claude/settings.json` mcpServers inject tool definitions into every prompt — even when irrelevant — costing 5-10K tokens pe Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -I https://raw.githubusercontent.com The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 542 lines · 17 tokens per session scan C ae8f57df5d8d
setup is a command published in the GitHub repository akaszubski/autonomous-dev (33 stars, last pushed yesterday), with no licence file. It adds 17 tokens to every session and 3,766 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 3 findings (reads agent configuration directories, reads mcp configuration, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
backlog
The project layer: milestones, epics, and user stories with refusing controllers — spec-seeded, sprint-ready.
sprint
Scope-boxed sprints over the backlog: one active sprint, explicit carry-over, a close that refuses to hide unfinished work.
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.
remediate
Close the debt the deterministic lanes cannot version-bump away: the grandfathered broken build, advisories with no direct upgrade path, the lint backlog, missing tests, missing docs. Each run plans that debt as finite work orders and works them in two tiers: deterministic recipes execute first at $0 (lockfile resync…
project
Unified project management. Handles detection, initialization, configuration, context generation, and environment loading.
research
Investigate a task and produce a structured research assessment for autonomous development.