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 SteveGJones/ai-first-sdlc-practices --skill kb-validate-citationsgit clone --depth 1 https://github.com/SteveGJones/ai-first-sdlc-practicesWrote 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/stevegjones/ai-first-sdlc-practices/kb-validate-citations)<a href="https://agentmods.dev/skills/stevegjones/ai-first-sdlc-practices/kb-validate-citations"><img src="https://agentmods.dev/badge/skills/stevegjones/ai-first-sdlc-practices/kb-validate-citations/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/stevegjones/ai-first-sdlc-practices/kb-validate-citations"><img src="https://agentmods.dev/badge/skills/stevegjones/ai-first-sdlc-practices/kb-validate-citations.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.00063 | $0.01659 |
| Opus 5.5 | $0.00025 | $0.00664 |
| Sonnet 5.5 | $0.00013 | $0.00332 |
| Haiku 4.5 | $0.00006 | $0.00166 |
Grade A, and why
kb-validate-citations scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sLI "https://doi.org/<doi>" -o /dev/null -w "%{http_code}" How it starts
The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate Knowledge Base Citations
Catch obvious citation hallucinations in library files. Deep research engines occasionally fabricate DOIs, attribute findings to the wrong author, or invent journal names. Manual spot-checking 10-20% of citations remains necessary; this skill automates the obvious failure cases so manual review can focus on subtler issues.
Argument
Optional file path or glob to scope validation. Default: all library files in library/**/*.md excluding the index files.
Examples:
library/dora-metrics.md— single filelibrary/dora-*.md— files matching a pattern- (no argument) — all library files
Preflight
- Verify the knowledge base is configured.
- Verify network access (DOI resolution requires HTTPS to https://doi.org).
Steps
1. Discover library files
Use Glob to find files matching the scope. Exclude:
library/_shelf-index.mdlibrary/_index.mdlibrary/log.mdlibrary/raw/**
2. Extract citations from each file
For each library file, parse the ## Key References section and the inline citations in ## Core Findings. Identify three citation types:
DOI citations — strings matching the DOI regex: 10\.\d{4,9}/[-._;()/:A-Z0-9]+ (case-insensitive). DOIs are the strongest signal because they're machine-resolvable.
arXiv IDs — strings matching arXiv:\d{4}\.\d{4,5} or arxiv\.org/abs/\d{4}\.\d{4,5}.
Journal references — anything matching the pattern <authors>. (<year>). "<title>." <Journal Name>, <volume>(<issue>), <pages>. or similar bibliographic format. Best-effort extraction; not all citations follow a standard format.
3. Validate each citation type
DOI resolution
For each DOI, attempt to resolve it via:
curl -sLI "https://doi.org/<doi>" -o /dev/null -w "%{http_code}"
Expected: HTTP 302 or 200 (redirected to the publisher landing page). Failure: HTTP 404 (DOI does not exist) or 500 (DOI registry error).
Classify each result:
- OK: 200/302
- NOT FOUND: 404 — flag as likely hallucinated
- TRANSIENT: 500/timeout/network failure — soft-fail with "could not verify"
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 First seen · 207 lines · 63 tokens per session scan A fe385f53ee0a
kb-validate-citations is a skill published in the GitHub repository SteveGJones/ai-first-sdlc-practices (41 stars, last pushed 15d ago), licensed MIT. It adds 63 tokens to every session and 1,659 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…