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/statusnpx skills add nick-railsback/skill-engine --skill statusgit 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.00033 | $0.02457 |
| Opus 5 | $0.00016 | $0.01229 |
| Sonnet 5 | $0.00007 | $0.00491 |
| Haiku 4.5 | $0.00003 | $0.00246 |
Grade A, and why
status 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Status
Read-only one-page dashboard. Lists fresh / stale / critical references by age, notes pending proposals waiting on human review, and surfaces any recent rejection-log clustering that suggests a doctrine gap.
Contextualizer root
Engine workflows operate inside a contextualizer installed as a project skill at one of three install levels:
- User-level:
~/.claude/skills/<slug>-context/ - Local-user-level:
~/.claude/local/skills/<slug>-context/(when in use) - Project-level:
<repo>/.claude/skills/<slug>-context/
Every path below — research/..., references/..., verify.sh —
resolves relative to whichever directory matches. Before reading
anything, locate the root by searching all three install levels in
order:
Run the script in shared/locator-block.md verbatim before proceeding.
Selecting a contextualizer
/skill-engine:status <name> names the contextualizer to report on:
<name> is the directory name without the -context suffix, the same
grammar review/apply/discard use. Substitute it (or the empty
string) for <name> in the locator above. With no argument,
auto-detection applies — it succeeds when exactly one contextualizer is
installed and lists the matches and exits when more than one is.
Read every subsequent research/foo path as $CTX_ROOT/research/foo,
every references/foo as $CTX_ROOT/references/foo, and verify.sh as
$CTX_ROOT/verify.sh.
Pending proposals
A staged-but-unapplied proposal sits as a sibling of the live tree at
${CTX_ROOT}.proposed/. STATUS surfaces it (and how far its review has
progressed) so a pending review does not silently rot — this is the
"notes pending proposals waiting on human review" the intro promises.
Read-only: STATUS reports the proposal's state but never advances it.
slug=$(basename "$CTX_ROOT"); slug="${slug%-context}"
proposed="${CTX_ROOT}.proposed"
if [ ! -d "$proposed" ]; then
printf 'No pending proposal (nothing staged).\n'
else
manifest="$proposed/.review/manifest.json"
review="$proposed/.review/REVIEW.md"
if [ -f "$manifest" ]; then
added=$(jq '[.entries[]|select(.status=="added")]|length' "$manifest" 2>/dev/null); added=${added:-0}
modified=$(jq '[.entries[]|select(.status=="modified")]|length' "$manifest" 2>/dev/null); modified=${modified:-0}
removed=$(jq '[.entries[]|select(.status=="removed")]|length' "$manifest" 2>/dev/null); removed=${removed:-0}
printf 'Pending proposal: %s.proposed/ (%s added, %s modified, %s removed)\n' \
"$slug" "$added" "$modified" "$removed"
else
printf 'Pending proposal: %s.proposed/ (incomplete — no manifest; DISCOVER/REFRESH did not finish)\n' "$slug"
fi
# Review progress, mirroring apply's pre-promotion gates (read-only here).
if [ -f "$review" ]; then
ticks=$(grep -ciE '^- \[x\] (reviewed|provisional|reject)' "$review" 2>/dev/null); ticks=${ticks:-0}
if grep -q '___' "$review" 2>/dev/null; then
printf ' Review: awaiting Step 1 predictions (run /skill-engine:review %s).\n' "$slug"
elif grep -qF '(Run /skill-engine:review' "$review" 2>/dev/null; then
printf ' Review: Step 1 filled; Step 2 not yet generated (re-run /skill-engine:review %s).\n' "$slug"
elif [ "$ticks" -eq 1 ]; then
state=$(grep -iE '^- \[x\] (reviewed|provisional|reject)' "$review" | head -1 | sed -E 's/^- \[[xX]\] +//')
printf ' Review: signed off as %s — ready for /skill-engine:apply %s.\n' "$state" "$slug"
else
printf ' Review: not yet signed off (tick one Step 3 box, then /skill-engine:apply %s).\n' "$slug"
fi
fi
fi
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 · 210 lines · 33 tokens per session scan A ca1a3d3b4c25
status is a skill published in the GitHub repository nick-railsback/skill-engine (2 stars, last pushed 25d ago), licensed MIT. It adds 33 tokens to every session and 2,457 once invoked, about $0.0002 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.
tech-design-generation
Generates professional Technical Design Documents following industry-standard engineering practices. This skill activates when the user asks to write a technical design, create an architecture design, draft a design doc, write a technical proposal, do system design, create a technical design document, write an RFC…
test-cases-generation
Generates structured test case sets with multi-dimensional coverage from project code analysis or specification documents. This skill activates when the user asks to write test cases, generate tests, supplement tests, create test coverage, or improve test completeness. It auto-scans the project to extract testable…
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/…
idea
Use when exploring a new idea before writing formal specifications. Guides users through iterative discovery, research, and critical analysis to crystallize vague ideas into validated requirement drafts. Includes anti-pseudo-requirement checks, competitive research, demand evidence gathering, and "What if we don't…