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 nick-railsback/skill-engine --skill skill-engine-contextgit clone --depth 1 https://github.com/nick-railsback/skill-engineWrote 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/nick-railsback/skill-engine/skill-engine-context)<a href="https://agentmods.dev/skills/nick-railsback/skill-engine/skill-engine-context"><img src="https://agentmods.dev/badge/skills/nick-railsback/skill-engine/skill-engine-context/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/nick-railsback/skill-engine/skill-engine-context"><img src="https://agentmods.dev/badge/skills/nick-railsback/skill-engine/skill-engine-context.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00106 | $0.02525 |
| Opus 5.5 | $0.00042 | $0.01010 |
| Sonnet 5.5 | $0.00021 | $0.00505 |
| Haiku 4.5 | $0.00011 | $0.00252 |
Grade A, and why
skill-engine-context 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context navigator
Overview
This navigator catalogs references for the source(s) registered with the engine. The navigator itself stays small; references load only when relevant to the current question.
When asked a question this navigator's domain covers:
- Scan the Catalog below for the matching topic.
- Follow the link to read the reference file.
- If the question spans multiple references, consult the Cross-reference map.
- If a reference points at a source URL for deeper detail, follow it only if the reference itself didn't answer the question.
Claims policy
Cite by default, and make load-bearing claims verifiable:
- Inline-cite every load-bearing claim with its SHA-pinned permalink, in the source forge's grammar — the link the reference gives for that fact (versions, defaults, signatures, deprecations, behavior a user could get wrong by guessing), for example on github.com
https://github.com/<owner>/<repo>/blob/<sha>/<path>#L<start>-L<end>. Put the permalink inline, on the claim. Use a bare filename parenthetical (e.g. (reference-name.md)) only when the reference genuinely provides no permalink. This inline permalink is what the grounded-citation eval (SELF-AUDIT Check 8) grades. - Don't cite orientational prose — "what is X?", "when did X launch?" — answer those from this navigator alone; opening a reference is itself a citation gesture.
- End with a one-line provenance footer, emitted italic, formatted
*References consulted: foo.md, bar.md. Grounded in {{LIBRARY}}@{{VERSION}} — [reference index]({{INDEX_URL}}).*The footer is a summary of what you read — not a substitute for the inline permalinks on the claims. The{{LIBRARY}}/{{VERSION}}/{{INDEX_URL}}tokens are agent-substituted at answer time, so they appear literally in the stampedSKILL.md. - If no reference was opened, say so in the footer ("Answered from general knowledge — no {{LIBRARY}} references consulted") — never fake it.
The voice is competent and careful — no "as an AI assistant" hedging.
What ships with it
22 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- .review/manifest.json 3.1 KB
- .review/REVIEW.md 5.5 KB
- evals/eval-viewer.html 8.7 KB
- evals/evals-test.json 2.8 KB
- evals/evals-train.json 6.4 KB
- evals/render-eval-results.sh 22 KB runs code
- evals/results-20260802T090208Z-59838.json 4.1 KB
- evals/run-eval.sh 24 KB runs code
- evals/run-note.md 1.5 KB
- references/nick-railsback-skill-engine-artifact-contract.md 23 KB
- references/nick-railsback-skill-engine-discover-refresh.md 27 KB
- references/nick-railsback-skill-engine-evaluation-and-audit.md 14 KB
- references/nick-railsback-skill-engine-invariants.md 15 KB
- references/nick-railsback-skill-engine-monorepo.md 14 KB
- references/nick-railsback-skill-engine-overview.md 14 KB
- references/nick-railsback-skill-engine-principles.md 8.7 KB
- references/nick-railsback-skill-engine-versioning.md 13 KB
- references/nick-railsback-skill-engine-workflows.md 20 KB
- research/.research-state.json 22 B
- research/review-state.json 97 B
- research/source-paths.json 475 B
- verify.sh 107 KB runs code
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 Changed · +1 lines · +11 tokens per session 86021e509dae
- 1mo ago Changed aa304289918e
- 1mo ago First seen · 105 lines · 95 tokens per session scan A 68eebb0b7773
skill-engine-context is a skill published in the GitHub repository nick-railsback/skill-engine (2 stars, last pushed 6d ago), licensed MIT. It adds 106 tokens to every session and 2,525 once invoked, about $0.0004 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-31.
Other skills, from other repositories
product-discovery
File-first orchestrator for product discovery and spec frameworks. Frames the problem with a Discovery Lead, Product Analyst, or System Architect role. Spawns parallel framework agents (Double Diamond, How Might We, Jobs to Be Done, user stories with INVEST, EARS for AI-coder specs, Gherkin), synthesizes into a PRD or…
meta-prompt-optimizer
Audit and rewrite prompts against Claude Opus 4.7 instruction-following best practices. Produces a scored audit plus a rewritten prompt. Use when the user asks to audit, review, critique, rewrite, improve, optimize, tighten, score, fix, migrate, or draft a prompt — including system prompts, CLAUDE.md files, Claude…
product-strategy
File-first orchestrator for business and product strategy frameworks. Frames the challenge with a CPO / CSO / VP Design role, spawns parallel framework agents (Rumelt kernel + Crux, Wardley Maps, Minto Pyramid as thinking structure, Working Backwards PR-FAQ as discovery artifact), synthesizes outputs into one strategy…
research
Multi-agent research skill. Decomposes a question into 2–4 parallel Opus 4.7 research agents that write findings to per-agent Markdown files in real time, then runs a synthesis agent to merge by theme. Use when the user wants to research a topic, investigate something, find comparisons, compare options, learn about a…
ultraplan
Generator-critic planning. Launches 3 parallel Opus 4.7 explorers with distinct divergence vectors (architectural, speed-first, simple-first), each producing an independent plan, then runs a critic synthesis that composes the best elements into a single plan with per-decision attribution. Defeats single-agent…
product-design-shared
Shared canonical references for product-design frameworks — Pyramid Principle, Working Backwards, Double Diamond, research design, methodology selection. Consumed by product-discovery, product-strategy, working-backwards, and customer-research via ${ERPAVALHOME}/skills/product-design-shared/references/. Do NOT invoke…