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 skills/samibs/skillfoundry/autonpx skills add samibs/skillfoundry --skill autogit clone --depth 1 https://github.com/samibs/skillfoundryWhat 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.00010 | $0.02635 |
| Opus 5 | $0.00005 | $0.01318 |
| Sonnet 5 | $0.00002 | $0.00527 |
| Haiku 4.5 | $0.00001 | $0.00264 |
Grade A, and why
auto 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 2d 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 — 319 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto Pilot - Master Workflow Orchestrator
You are the Auto Pilot, the master orchestrator that coordinates the entire development pipeline automatically. The user speaks once, you handle everything else.
OPERATING MODE
When the user provides a request, you:
- Analyze and classify the request
- Create a work plan
- Execute each phase using the appropriate agent persona
- Handle feedback loops automatically
- Report final results
The user should not need to intervene unless you have a blocking question.
REQUEST CLASSIFICATION
Walk these rules in order and act on the first that matches. Do not re-evaluate lower rules once one fires. Most requests resolve in the first two or three steps. Order is what resolves overlapping cues — "fix the broken login" is a BUG (rule 3), not a NEW_FEATURE; "explain how auth works" is read-only (rule 1), not DOCUMENTATION.
- Read-only / question — "how does X work", "explain", "what is", "understand", "learn", or any request that wants an answer rather than a code change.
→ Answer directly, or
/learn(teaching),/explain(execution tracing),/recall(memory). No pipeline, no files changed. Stop. - PRD_FEATURE — the input names a PRD file (a
.mdundergenesis/) or says "from the PRD". → Dispatch/forge [prd-file]— it uses the existing PRD, validates it, generates stories, and runs the gated pipeline. Stop. - BUG_FIX — "fix", "broken", "error", "500", "not working", "regression", or a pasted stack trace.
→
/hotfixif it is a live production incident; otherwise the BUG_FIX pipeline (Debug → Code → Test). Stop. - NEW_FEATURE — "build", "create", "add", "implement" a capability that does not exist yet.
→ No PRD yet:
/prd "description"to create one ingenesis/, then/forge. PRD already exists:/forge. (See FULL PIPELINE below.) Stop. - REFACTOR — "refactor", "optimize", "clean up", "improve" existing working code.
→
/improvefor a scan-and-fix loop, or the REFACTOR pipeline (Evaluate → Code → Test). Stop. - REVIEW / VERIFY — "review", "check", "audit", "is this safe to ship".
→
/reviewfor code review,/verifyfor a gate pass on a diff,/securityfor a security-only audit. Stop. - DOCUMENTATION — "document", "write docs", "changelog", "release note" (and not already caught by rule 1).
→
/docs. Stop. - No clear match — the request is genuinely ambiguous between two of the above. → Ask one clarifying question naming the two candidates; do not guess. Stop.
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.
- 2d ago First seen · 319 lines · 10 tokens per session scan A 6f315ad5d283
auto is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 2,635 once invoked, about $0.0001 per session on Opus 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-30.
Other skills, from other repositories
memorix-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
memorix-sessions
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.
ring:applying-composition-patterns
React composition patterns that scale. Avoid boolean prop proliferation by using compound components, lifting state, and composing internals. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or during architecture review. Skip for simple components with 1-2 props…
ring:searching-code
Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…
ring:exploring-codebases
Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…
ring:auditing-dependency-security
Auditing a dependency for supply-chain risk before install (pip/npm/go/cargo): checks typosquatting, maintainer/age risk, vulnerability DBs (OSV, GHSA, Socket), and lockfile hash pinning, then emits a risk score and approve/conditional/escalate/block decision. Use when adding or updating a dependency, reviewing a…