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 DavidROliverBA/ArchitectKB --skill nfr-reviewgit clone --depth 1 https://github.com/DavidROliverBA/ArchitectKBWrote 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/davidroliverba/architectkb/nfr-review)<a href="https://agentmods.dev/skills/davidroliverba/architectkb/nfr-review"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/nfr-review/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/davidroliverba/architectkb/nfr-review"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/nfr-review.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00017 | $0.02757 |
| Opus 5 | $0.00009 | $0.01378 |
| Sonnet 5 | $0.00003 | $0.00551 |
| Haiku 4.5 | $0.00002 | $0.00276 |
Grade A, and why
nfr-review 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 11d 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 — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/nfr-review
Review an existing HLD from Confluence against the NFR YAML reference and generate a gap report with scoring and remediation recommendations. Uses parallel sub-agents for efficient analysis.
Usage
/nfr-review ERPSystem
/nfr-review "AlertHub" CS1
/nfr-review 664765269 CS2 confluence
/nfr-review https://britishairways.atlassian.net/wiki/spaces/BDOC/pages/12345 CS2
Data Source
NFR reference data: .claude/data/nfr-reference.yaml — single source of truth for all 66 NFRs.
Scoring Rubric (0-3 Scale)
| Score | Rating | Meaning |
|---|---|---|
| 3 | Explicitly Addressed | NFR requirement clearly documented with specific evidence, links, or implementation details |
| 2 | Mentioned | NFR topic discussed but lacking evidence, specifics, or measurable targets |
| 1 | Implied | Related concept mentioned but NFR not explicitly addressed; may be inferred from context |
| 0 | Not Covered | NFR not mentioned at all; no evidence of consideration |
| N/A | Not Applicable | NFR section does not apply to this system (e.g., PCI for non-payment system) |
Instructions
Phase 1: Load NFR Reference
- Read
.claude/data/nfr-reference.yaml - Parse all 66 NFRs with their requirements, tier values, and evidence guidance
- Note the section applicability matrix
Phase 2: Fetch the HLD
- Resolve the system HLD using Atlassian MCP tools:
- If argument is a URL with
pageId: extract ID and usegetConfluencePage - If argument is a numeric ID: use
getConfluencePagedirectly - If argument is a system name: search for "[System Name] HLD" or "High-Level Design" in Confluence
- Search pattern:
searchConfluenceUsingCqlwithtitle ~ "[system] HLD" OR title ~ "[system] High-Level Design"
- If argument is a URL with
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.
- 11d ago First seen · 290 lines · 17 tokens per session scan A f28c3399b962
nfr-review is a skill published in the GitHub repository DavidROliverBA/ArchitectKB (52 stars, last pushed 6mo ago), licensed MIT. It adds 17 tokens to every session and 2,757 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
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…
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
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…