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/agentculture/arxivist/doc-test-alignmentnpx skills add agentculture/arxivist --skill doc-test-alignmentgit clone --depth 1 https://github.com/agentculture/arxivistWrote 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/agentculture/arxivist/doc-test-alignment)<a href="https://agentmods.dev/skills/agentculture/arxivist/doc-test-alignment"><img src="https://agentmods.dev/badge/skills/agentculture/arxivist/doc-test-alignment.svg" alt="Measured on agentmods" 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 | $0.00101 | $0.00631 |
| Opus 5 | $0.00051 | $0.00316 |
| Sonnet 5 | $0.00020 | $0.00126 |
| Haiku 4.5 | $0.00010 | $0.00063 |
Grade A, and why
doc-test-alignment 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 5d 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.
This is a copy
100% identical to doc-test-alignment — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
doc-test-alignment (stub)
This skill is a stub. The real workflow is intentionally not yet implemented —
the file exists so that steward verify can find it and so contributors who
land here know it is on the roadmap, not forgotten.
How to run
scripts/check.sh is the entry point. Today it prints a not-yet-implemented
notice and exits non-zero. When the workflow lands, the script will gate
PR-readiness on the alignment contract below; until then, treat any green
exit code from this script as a bug.
What it will check
The skill is the contract for four narrow alignments. README.md command
examples must still execute against the current checkout and produce output
that matches the surrounding prose. The "build/test/publish" command lines in
CLAUDE.md must do the same. For each .claude/skills/<name>/, the SKILL.md
description frontmatter must agree with what the scripts under
scripts/ actually do — surfacing disagreements (e.g. SKILL.md claims the
skill bumps versions but scripts/ has no bump script). And for each test,
the test name should still describe the assertions the test makes — flagging
drift where the name advertises a feature the assertions no longer touch.
Why it ships as a stub
Each of those four checks is independently non-trivial. Shipping a partial
implementation would either silently pass when it shouldn't, or false-positive
on intentional doc-vs-code differences. The right path is to land the checks
one at a time, with their own tests, behind a
steward verify --check doc-test-alignment flag. The parent verbs (verify,
doctor) are named in the "Roadmap" section of CLAUDE.md; the broader
sibling-pattern contract lives in docs/sibling-pattern.md.
What this stub guarantees today
- The skill directory exists, so
steward verify's skills-convention check finds the standard layout (SKILL.md +scripts/with an entry-point). scripts/check.shis the entry-point script, satisfying the steward skills convention requirement that every skill ships an executable script.- This
SKILL.mdis the contract for what the skill will do — when the implementation lands, it must satisfy this description or the description must move first.
What ships with it
1 file 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.
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.
- 5d ago First seen · 57 lines · 101 tokens per session scan A 30b43ee97999
doc-test-alignment is a skill published in the GitHub repository agentculture/arxivist (2 stars, last pushed 1mo ago), licensed MIT. It adds 101 tokens to every session and 631 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to doc-test-alignment, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…