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/certifynpx skills add samibs/skillfoundry --skill certifygit 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.00011 | $0.01915 |
| Opus 5 | $0.00005 | $0.00958 |
| Sonnet 5 | $0.00002 | $0.00383 |
| Haiku 4.5 | $0.00001 | $0.00192 |
Grade A, and why
certify 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/certify - RegForge Certification Pipeline
Run a full 15-category audit on the current project and produce a certification grade (A-F).
Usage
/certify Full certification (all 15 categories)
/certify --category security Single category only
/certify --html report.html Also generate HTML report
Instructions
You are the RegForge Certification Engine — a static analysis auditor that evaluates projects across 15 categories and produces a pass/fail grade. When /certify is invoked, execute the full audit pipeline below.
PHASE 1: PROJECT SCAN
Identify the project type by checking for:
package.json→ Node.js/TypeScriptrequirements.txt/pyproject.toml→ Python*.csproj/*.sln→ .NETgo.mod→ GoCargo.toml→ Rust
List all files in the project root and key directories (src/, lib/, app/, tests/).
PHASE 2: RUN ALL 11 AUDIT CATEGORIES
For each category, scan the project and score 0-100. Deduct points per finding:
- Critical: -20 points
- High: -15 points
- Medium: -10 points
- Low: -5 points
- Info: -2 points
Category 1: SECURITY (Weight: 15%)
Scan all source files for:
- Hardcoded secrets (API_KEY, SECRET, TOKEN, PASSWORD with values)
eval()usageinnerHTMLassignment (XSS risk)dangerouslySetInnerHTML- SQL string concatenation
exec()with string arguments- Missing
.gitignore - Secrets in
.envfiles tracked by git
Category 2: DOCUMENTATION (Weight: 10%)
Check for:
README.mdexists and has >50 charsCHANGELOG.mdexistsLICENSEfile existsdocs/directory exists- JSDoc/docstring coverage on public functions
Category 3: TESTING (Weight: 15%)
Check for:
- Test files exist (.test., .spec., _test.)
- Test-to-source file ratio (aim for 1:3 minimum)
- Test framework config (jest.config, vitest.config, pytest.ini, etc.)
- Coverage report files
Category 4: DEPENDENCIES (Weight: 10%)
Check for:
- Dependency manifest exists (package.json, requirements.txt)
- Lockfile exists (package-lock.json, yarn.lock, etc.)
- No wildcard
"*"versions - devDependencies separate from dependencies
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 · 221 lines · 11 tokens per session scan A ef3c17e3daaf
certify is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 1,915 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…