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-jira-epicgit 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-jira-epic)<a href="https://agentmods.dev/skills/davidroliverba/architectkb/nfr-jira-epic"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/nfr-jira-epic/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-jira-epic"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/nfr-jira-epic.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.00027 | $0.01438 |
| Opus 5 | $0.00014 | $0.00719 |
| Sonnet 5 | $0.00005 | $0.00288 |
| Haiku 4.5 | $0.00003 | $0.00144 |
Grade A, and why
nfr-jira-epic 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/nfr-jira-epic
Create a Jira Epic with one story per applicable NFR, turning the NFR compliance table into trackable sprint work. Each story includes the requirement, evidence guidance, and acceptance criteria.
Usage
/nfr-jira-epic ERPSystem CS1 all,gdpr
/nfr-jira-epic "AlertHub" CS1 all,gdpr ARCH
/nfr-jira-epic DataPlatform CS2 all,pci,gdpr,caa_nis
Data Source
All NFR data is read from .claude/data/nfr-reference.yaml — the single source of truth for all 66 NFRs. Do NOT hard-code NFR content; always read from the YAML.
Prerequisites
- Atlassian MCP tools must be available (Jira access via
createJiraIssue) - User must have permissions to create issues in the target Jira project
Instructions
Phase 1: Load NFR Data
- Read
.claude/data/nfr-reference.yaml - Parse sections and NFRs
- Read
.claude/data/nfr-evidence-rules.yamlfor automated check references
Phase 2: Filter NFRs
- Parse the
typesargument into a list (split on comma) - Always include
allin the types list - Filter sections by applicability (same logic as
/nfr-capture) - Map CS tier to SL tier: CS1→SL1, CS2→SL2, CS3→SL3, CS4→SL4
Phase 3: Determine Jira Project
If project argument is provided, use it. Otherwise, ask the user:
Which Jira project should the NFR Epic be created in?
Enter the Jira project key (e.g., ARCH, ENG, OPS):
Phase 4: Create Epic
Use the Atlassian MCP createJiraIssue tool to create the Epic:
- Issue Type: Epic
- Project: [project key]
- Summary:
NFR Compliance — [System Name] ([CS tier]/[SL tier]) - Description:
h2. NFR Compliance Epic
*System:* [System Name]
*Classification:* [CS tier] / [SL tier]
*Applicability:* [types list]
*Sections:* [included count] of 13
*NFRs:* [included NFR count] of 66
This epic tracks NFR compliance for [System Name] as defined in the BA NFR Template (Confluence page 664765269, v0.2).
Each story represents one NFR requirement. Stories close when evidence is attached and reviewed.
*Generated by:* /nfr-jira-epic skill
*NFR Reference:* .claude/data/nfr-reference.yaml
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 · 173 lines · 27 tokens per session scan A b907d9703470
nfr-jira-epic is a skill published in the GitHub repository DavidROliverBA/ArchitectKB (52 stars, last pushed 6mo ago), licensed MIT. It adds 27 tokens to every session and 1,438 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.