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 skills/samibs/skillfoundry/docsWrote 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/skills/samibs/skillfoundry/docs)<a href="https://agentmods.dev/skills/samibs/skillfoundry/docs"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/docs/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/skills/samibs/skillfoundry/docs"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 232 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 606 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00026 | $0.06314 |
| Opus 5.5 | $0.00010 | $0.02526 |
| Sonnet 5.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 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 — 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.
- 1mo 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 14d ago), licensed MIT. It adds 26 tokens to every session and 6,314 once invoked, about $0.0001 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-30.
Other skills, from other repositories
ring:migrating-to-lib-observability
Migrating a Lerian Go app off lib-commons observability imports (deprecated shims or removed APIs) to lib-observability via a fixed mapping table, then bumps go.mod and validates the build; ring:backend-go applies the edits. Covers log/zap/runtime/assert, opentelemetry/tracing, HTTP middleware, context helpers, and…
memorix-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
ring:planning-codebase-simplification
Planning a whole-codebase simplification: audits a Go/TS codebase for needless abstraction and emits a KILL/REVIEW/KEEP plan plus a ring:running-dev-cycle task array. Plans only — no edits. Detects single-impl interfaces, pass-through shims, translation-free adapters, and dead-code cascade chains under an inverted…
ring:planning-large-features
Planning the 8-gate Large Track pre-dev workflow (research, PRD, feature map, TRD, API contract, data model, dependency map, plan) with per-gate human approval. Use for features 2+ days that add dependencies, data models, multi-service integration, or new architecture. Skip for small features (use…
ring:generating-llms-txt
Generating or auditing a repository's llms.txt per the llmstxt.org spec, and creating CLAUDE.md / AGENTS.md when missing, by analyzing README, build files, docs, and API surface. Use when creating an llms.txt, auditing an existing one for spec compliance and live links, or improving a repo's AI readability. Skip when…
ring:checking-frontend-quality
Checking frontend quality against changed UI via ring:qa-frontend in accessibility, visual, e2e, or performance mode and aggregating pass/fail verdicts. Use when a frontend change needs standalone a11y, visual-snapshot, Playwright e2e, or Lighthouse/Core-Web-Vitals validation outside the dev cycle. Skip for…