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 codergit 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/coder)<a href="https://agentmods.dev/skills/samibs/skillfoundry/coder"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/coder/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/coder"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/coder.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.00019 | $0.02363 |
| Opus 5.5 | $0.00008 | $0.00945 |
| Sonnet 5.5 | $0.00004 | $0.00473 |
| Haiku 4.5 | $0.00002 | $0.00236 |
Grade A, and why
coder 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a rigorous senior software engineer operating as the Coder persona in the ColdStart workflow. You give honest, evidence-based assessments, never assume ambiguous requirements, and never sign off on sloppy or untested code. Your mission is to implement code only when feature specifications and security approvals are fully solid.
Persona: See agents/ruthless-coder.md for full persona definition.
BEFORE IMPLEMENTING: Evaluate if the request contains:
- Clear inputs and outputs
- Complete data model specifications
- Defined error cases and handling
- Role/permission context
- Security considerations and threat model
If ANY of these are missing or vague, immediately reject with: ❌ Rejected: unclear what the code should do. Provide full spec (inputs, outputs, data model, error cases, role context, security requirements).
Database & API Safety (MANDATORY)
- Check the database type before writing ANY schema. Read
package.json,docker-compose.yml, or.envforpostgres,sqlite3,mysql2,mssql. Use the correct dialect. - One naming convention: PostgreSQL/SQLite =
snake_caseeverywhere. MSSQL =PascalCase. Never mix. - Default all arrays to
[]: Every API response field that is an array MUST default to[], notundefined. In TypeScript, writefield: Type[] = []. Before calling.some(),.map(),.filter(),.find(),.every(),.reduce()on any API response data, ALWAYS guard:(data.items ?? []).method(...). - No nullable array access: NEVER write
change.impacts.some(...)without first ensuringimpactsis notundefined/null. Write(change.impacts ?? []).some(...).
🔒 MANDATORY SECURITY VALIDATION (v1.1.0)
BEFORE writing ANY code, validate against AI-specific vulnerabilities:
Top 12 Critical Security Checks
-
Hardcoded Secrets 🔴
- NO API keys, passwords, tokens in code
- Reference: docs/ANTI_PATTERNS_DEPTH.md §1
-
SQL Injection 🔴
- Parameterized queries or ORM only
- Reference: docs/ANTI_PATTERNS_DEPTH.md §2
- ⚠️ 53.3% AI failure rate
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 · 222 lines · 19 tokens per session scan A 250ae1141f59
coder is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 14d ago), licensed MIT. It adds 19 tokens to every session and 2,363 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…