Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/samibs/skillfoundrynpx agentmods add commands/samibs/skillfoundry/autonomousWrote 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/samibs/skillfoundry/autonomous)<a href="https://agentmods.dev/commands/samibs/skillfoundry/autonomous"><img src="https://agentmods.dev/badge/commands/samibs/skillfoundry/autonomous/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/samibs/skillfoundry/autonomous"><img src="https://agentmods.dev/badge/commands/samibs/skillfoundry/autonomous.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.00000 | $0.00768 |
| Opus 5.5 | $0.00000 | $0.00307 |
| Sonnet 5.5 | $0.00000 | $0.00154 |
| Haiku 4.5 | $0.00000 | $0.00077 |
Grade A, and why
autonomous 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.
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/autonomous - Toggle Autonomous Developer Loop
Toggle autonomous mode on/off. When active, every user input is automatically classified and routed to the correct pipeline without manual command invocation.
Usage
/autonomous Show current status
/autonomous on Enable autonomous mode
/autonomous off Disable autonomous mode
/autonomous status Show detailed status with sync info
Instructions
You manage the autonomous developer loop toggle. When invoked:
/autonomous or /autonomous status
Check the current state and report:
# Check if autonomous mode is active
FLAG_FILE=".claude/.autonomous"
Display:
Autonomous Mode: [ON/OFF]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Protocol: agents/_autonomous-protocol.md
Classifier: agents/_intent-classifier.md
Mode: [ACTIVE — all inputs auto-routed / INACTIVE — manual commands]
Knowledge Sync: [RUNNING (PID: XXXX) / STOPPED]
Last Sync: [timestamp or "never"]
Sync Repo: [repo URL or "not configured"]
Session Stats:
Inputs classified: [N]
Pipelines executed: [N]
User corrections: [N]
/autonomous on
-
Create the flag file:
mkdir -p .claude echo '{"enabled":true,"activated":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'","version":"1.0"}' > .claude/.autonomous -
Verify the protocol files exist:
agents/_autonomous-protocol.md— routing rulesagents/_intent-classifier.md— classification reference
-
Start the knowledge sync daemon if configured:
if [ -f scripts/knowledge-sync.sh ] && [ -x scripts/knowledge-sync.sh ]; then bash scripts/knowledge-sync.sh start --if-not-running fi -
Display:
Autonomous Mode: ON ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ The autonomous developer loop is now active. Every input will be classified and routed automatically. How it works: You type → Claude classifies (FEATURE/BUG/REFACTOR/QUESTION/OPS/MEMORY) Claude runs → The appropriate pipeline executes fully You review → Structured summary presented for approval To disable: /autonomous off
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 · 124 lines · 0 tokens per session scan A 778426832c33
autonomous is a command published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 768 tokens. 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-09-03.
Other commands, from other repositories
follow-up
Review and act on pending reminders. Bare invocation shows all reminders as an indexed list; cron-fired invocation (/follow-up due ) surfaces the specific reminder and waits for a response; /follow-up review lists stale project follow-up entries for per-item disposition (extend/close/promote/skip). Transport-aware…
voice
Integrar con Claude Code Voice Mode para dictar specs y requirements por voz. Usa cuando el usuario dice "voice", "dictar", "dictate specs", "voice mode", "dictar requerimientos", "speech to text", "voice input", "hablar specs", "dictate", "voice integration". Configura Voice Mode para dictar specs y requirements sin…
journal
Show the activity journal — recent file edits, commands, and actions from this and previous sessions.
note
Zero-friction idea capture. Append, list, or promote notes to todos.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.