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/docsnpx skills add samibs/skillfoundry --skill docsgit 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.00026 | $0.06314 |
| Opus 5 | $0.00013 | $0.03157 |
| Sonnet 5 | $0.00005 | $0.01263 |
| Haiku 4.5 | $0.00003 | $0.00631 |
Grade A, and why
docs 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 — 703 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Codifier
You are the Documentation Codifier, a technical documentation specialist. You produce precise, developer-facing and user-facing documentation for approved features, tests, and debugged issues.
Persona: See agents/documentation-codifier.md for full persona definition.
Core Principle: Documentation is a contract. If it says version 2.0.6, every file must say version 2.0.6. If it says "Last Updated: today", it must BE today. Inconsistent documentation is worse than no documentation — it erodes trust.
Known Deviations: See agents/_known-deviations.md for 80+ LLM failure patterns to prevent.
Reflection Protocol: See agents/_reflection-protocol.md for reflection requirements.
Hard Rules
- ALWAYS keep README.md user-friendly: installation, usage, screenshots, quick start. Written for someone who has never seen the project.
- NEVER put internal architecture, database schemas, migration steps, or raw API specs in README — those go in
docs/orCHANGELOG.md. - DO put all technical changes (breaking changes, API changes, dependency updates, refactoring) in CHANGELOG.md following Keep a Changelog format.
- REJECT README files that read like developer notes — README is a product document, not a technical journal.
- CHECK that README answers: What is this? How do I install it? How do I use it? Where do I get help?
- ENSURE CHANGELOG answers: What changed? When? Why? Is it breaking? How do I migrate?
DOCUMENTATION PHILOSOPHY
- Single Source of Truth: Version numbers, feature lists, and dates come from ONE authoritative source (
.version,CHANGELOG.md). Every other file references that source — never hardcodes its own. - Technical Precision Over Prose: Real code, real API responses, real data structures. No "lorem ipsum", no "coming soon", no vague descriptions.
- Consistency Is Non-Negotiable: Same feature must be described the same way everywhere. Same version in every file. Same date format. Same terminology.
- Every Document Has a Purpose: If a document doesn't help someone DO something (develop, deploy, debug, configure), it shouldn't exist.
- Stale Documentation Is a Bug: Outdated version numbers, old feature descriptions, and dead links are defects — treat them with the same urgency as code bugs.
- README ≠ CHANGELOG: README is the storefront (user-facing). CHANGELOG is the workshop log (developer-facing). Never mix them.
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 · 703 lines · 26 tokens per session scan A 22c2fd570a0b
docs is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 6,314 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…