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/nick-railsback/skill-engine/skill-engine-contextnpx skills add nick-railsback/skill-engine --skill skill-engine-contextgit clone --depth 1 https://github.com/nick-railsback/skill-engineWhat 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.00095 | $0.02402 |
| Opus 5 | $0.00048 | $0.01201 |
| Sonnet 5 | $0.00019 | $0.00480 |
| Haiku 4.5 | $0.00010 | $0.00240 |
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 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 — 105 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 — the
https://github.com/<owner>/<repo>/blob/<sha>/<path>#L<start>-L<end>link the reference gives for that fact (versions, defaults, signatures, deprecations, behavior a user could get wrong by guessing). 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 1.7 KB
- .review/REVIEW.md 4.6 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 14 KB runs code
- evals/results-20260802T090208Z-59838.json 4.1 KB
- evals/run-eval.sh 11 KB runs code
- evals/run-note.md 1.5 KB
- references/nick-railsback-skill-engine-artifact-contract.md 18 KB
- references/nick-railsback-skill-engine-discover-refresh.md 21 KB
- references/nick-railsback-skill-engine-evaluation-and-audit.md 12 KB
- references/nick-railsback-skill-engine-invariants.md 13 KB
- references/nick-railsback-skill-engine-monorepo.md 11 KB
- references/nick-railsback-skill-engine-overview.md 11 KB
- references/nick-railsback-skill-engine-principles.md 8.7 KB
- references/nick-railsback-skill-engine-versioning.md 9.8 KB
- references/nick-railsback-skill-engine-workflows.md 14 KB
- research/.research-state.json 22 B
- research/review-state.json 97 B
- research/source-paths.json 475 B
- verify.sh 61 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.
- 2d 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 25d ago), licensed MIT. It adds 95 tokens to every session and 2,402 once invoked, about $0.0005 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-31.
Other skills, from other repositories
skill-creator
Create or improve Zhin Agent skills (SKILL.md). Use when asked to add a skill, write SKILL.md, document a repeatable agent workflow, or refine skill frontmatter/keywords. Triggers: 创建技能, 写 SKILL, skill-creator, 加 skill.
skill-sync-checker
Detects content drift between skill files and their source documents. Helps maintain skills that are derived from other documentation by comparing content and flagging outdated sections.
erpaval
Workflow for autonomous software development with the Kiro CLI (open Agent Skills standard). Classifiers route scope, complexity, directory state, and spec readiness before committing to Explore / Research / Plan / Act / Validate, then close the loop with a Compound step that persists lessons to .erpaval/solutions/…
skill-creator
Guide for creating effective agent skills. Use when you want to create a new skill, improve an existing skill, or learn best practices for skill development. Helps codify learned patterns into reusable, discoverable skills.
agent-ux-patterns
Agent UX patterns and human-in-the-loop design: Twilio A2H protocol, Levels of Autonomy (L0-L5), inbox pattern, progressive trust, decision journal, gate reviews, autonomous work reports. Six-phase methodology from vague pain point to concrete data model via landscape research and multi-direction brainstorming. Use…
Agent Instruction Drift Check
Procedure for comparing an agent-facing instruction doc (AGENTS.md/CLAUDE.md-style) against the actual current code and configuration to find and flag mismatches.