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 skills add samibs/skillfoundry --skill certifygit clone --depth 1 https://github.com/samibs/skillfoundryWrote 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/certify)<a href="https://agentmods.dev/skills/samibs/skillfoundry/certify"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/certify/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/certify"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/certify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00011 | $0.01915 |
| Opus 5.5 | $0.00004 | $0.00766 |
| Sonnet 5.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 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 — 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.
- 1mo 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 14d ago), licensed MIT. It adds 11 tokens to every session and 1,915 once invoked, about $0.0000 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…