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 Rainnystone/naive-harness-kit --skill nhk-archivegit clone --depth 1 https://github.com/Rainnystone/naive-harness-kitWrote 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/rainnystone/naive-harness-kit/nhk-archive)<a href="https://agentmods.dev/skills/rainnystone/naive-harness-kit/nhk-archive"><img src="https://agentmods.dev/badge/skills/rainnystone/naive-harness-kit/nhk-archive/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/rainnystone/naive-harness-kit/nhk-archive"><img src="https://agentmods.dev/badge/skills/rainnystone/naive-harness-kit/nhk-archive.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.00025 | $0.00870 |
| Opus 5 | $0.00013 | $0.00435 |
| Sonnet 5 | $0.00005 | $0.00174 |
| Haiku 4.5 | $0.00003 | $0.00087 |
Grade A, and why
nhk-archive 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 4d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NHK Archive
Use this skill only for the active-to-archive transition of one completed workstream.
Router Handoff
Reuse a welcome-to-nhk handoff only when it is for the current workspace and current NHK run, and its Route selects this skill. If the handoff is absent, unresolved, or stale, run welcome-to-nhk first. If it selects another route, hand off and do not continue archive.
Use the handoff's dependency, instruction, topology, and complete-foundation state as the archive input. Do not persist the handoff. A bootstrap route must finish and rerun welcome-to-nhk before archive may resume.
Human Archive Gate
- If the current context does not already contain a clear yes for this specific workstream, ask whether to archive it now.
- Do not move, rename, copy into archive, reset, or clear anything before that yes.
- If the user declines or remains ambiguous, keep the workstream active and stop.
Workstream Identity And Materials
Choose one stable identity already supported by the active materials, such as a dated topic slug, plan/spec name, initiative, or user-provided name. If multiple identities remain plausible, ask.
Select related materials in this order:
- active spec and plan surfaces used by the installed or explicitly adopted planning workflow
- active root tracking such as
task_plan.md,progress.md, andfindings.md - filenames, directories, dates, and topic slugs matching the chosen identity
- file content and current context when naming signals are incomplete
Archive only materials that clearly belong to that identity. Completed implementation plans may move with their workstream, but the stable companions coding-agent-guide.md, implementation-planning.md, worker-policy.md, execution-recovery.md, and documentation-governance.md never do. Do not archive unrelated live plans, shared instruction or governance docs, or tracking still used by another workstream.
Naming And Index Contract
When creating or repairing the archive index row, read ../references/archive-readme-template.md. Do not load unrelated instruction or companion templates during archive.
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.
- 4d ago Changed 26d606f7474f
- 10d ago First seen · 60 lines · 25 tokens per session scan A 9df87a177a3c
nhk-archive is a skill published in the GitHub repository Rainnystone/naive-harness-kit (21 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 870 once invoked, about $0.0001 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-30.
Other skills, from other repositories
merge-review
Reviews pending fleet worktree merges before they're accepted. Reads the merge-check queue, detects file-level conflicts between branches, proposes a safe merge order, and surfaces reconciliation plans for overlapping changes.
workspace
Multi-repo campaign coordinator. Same lifecycle as fleet -- scope claims, discovery relay, wave-based execution -- but the unit of work is a repo, not a file. Coordinates campaigns across repositories with shared context.
decision-map
Turn a loose idea into a git-tracked, session-resumable map of typed investigation tickets, then drive them to resolution one at a time. The planning-loop engine for work that is still being figured out — too fuzzy for a campaign, too big for a single intake item. Resolved tickets graduate into .planning/intake/ for…
unharness
Safely leave Citadel using the active adoption receipt. Produces a no-write, reviewable plan, preserves a portable archive, removes only exact owned material, and reports modified or externally registered surfaces as retained or unknown. Legacy installs must be imported before exact leave is claimed.
fo-status-viewer
First-officer status query/mutate/display surface — the status command flag docs, --set field docs, canonical captain-facing invocations, the Captain-Facing State Display rendering, and the GitHub-issue-filing approval gate. Invoke at the first ad-hoc status question, --set mutation, --next-id/--resolve lookup, or…
passdown-intake
Use when processing captured notes/ideas from an inbox into actionable work — scans inbox notes, clarifies intent with the user, routes each note to its target repo, creates a planning artifact (e.g. an OpenSpec change), and marks the note processed.