Borrowing it
Nothing to install: this file belongs to GSA-TTS/agentic-coding-playbook. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/GSA-TTS/agentic-coding-playbook/main/.agents/skills/federal-decision-records/SKILL.mdgit clone --depth 1 https://github.com/GSA-TTS/agentic-coding-playbookWrote 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/gsa-tts/agentic-coding-playbook/federal-decision-records)<a href="https://agentmods.dev/skills/gsa-tts/agentic-coding-playbook/federal-decision-records"><img src="https://agentmods.dev/badge/skills/gsa-tts/agentic-coding-playbook/federal-decision-records/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/gsa-tts/agentic-coding-playbook/federal-decision-records"><img src="https://agentmods.dev/badge/skills/gsa-tts/agentic-coding-playbook/federal-decision-records.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.00027 | $0.01758 |
| Opus 5 | $0.00014 | $0.00879 |
| Sonnet 5 | $0.00005 | $0.00352 |
| Haiku 4.5 | $0.00003 | $0.00176 |
Grade A, and why
federal-decision-records 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 10d 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Federal Decision Records
This skill helps users create, validate, and index architectural and security decision records using MADR (Markdown Any Decision Records) format with federal compliance extensions.
Decision records provide an audit trail linking design choices to NIST controls and risk treatment rationale — required for ATO documentation.
When to Use
- Documenting a decision about AI agent authorization or capabilities
- Recording data handling or classification decisions
- Capturing deployment or infrastructure security choices
- Documenting cryptographic or authentication design decisions
- Preparing audit trail for ISSO or ATO reviewer
- When the
federal-risk-assessmentskill identifies risks that require treatment decisions — document the treatment rationale here
How It Works
This skill has three modes:
- Create — Guide the user through creating a new decision record
- Validate — Check existing ADRs for format and completeness
- Index — Generate a decision record index from frontmatter
Ask the user which mode they need, or infer from context.
Mode 1: Create a Decision Record
Step 1: Determine Decision Category
Ask the user what kind of decision they are documenting. Present the categories from references/DECISION_CATEGORIES.md:
"What category does this decision fall into?"
Read references/DECISION_CATEGORIES.md to present the current category list
with examples. Each category maps to relevant NIST controls.
Step 2: Collect Decision Metadata
Ask for the required fields:
"Let's document this decision. I need:
- Title — What is being decided? (Use format: 'Use X for Y')
- Status — proposed, accepted, deprecated, or superseded?
- Decision makers — Who is involved in this decision?
- Date — When was this decided? (Default: today)"
Step 3: Collect Federal Compliance Fields
These extend standard MADR with federal context:
What ships with it
2 files 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.
- 10d ago First seen · 212 lines · 27 tokens per session scan A 9e7872ed09b2
federal-decision-records is a skill published in the GitHub repository GSA-TTS/agentic-coding-playbook (25 stars, last pushed today), licensed CC0-1.0. It adds 27 tokens to every session and 1,758 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
html-ppt-zhangzara-stencil-tablet
A workplace-safety compliance review for a manufacturing regulator — findings, the evidence chain, and the corrective mandate. Built as a decision-grade policy briefing deck for regulator, plant leadership.
treatment-plans
Format and structurally validate local treatment-plan documentation after clinical decisions have already been supplied and verified by authorized licensed professionals. Use for source traceability, clinician-authored intervention records, goals and checkpoints, shared-decision records, reconciliation handoffs, and…
handbook-updates
Diff a proposed handbook change against the current version, flag ripple effects and state supplement impacts. Use when user says "update the handbook", "add this to the handbook", "handbook change", or has a policy ready for insertion.
software-copyright-materials
A workflow for creating Chinese application materials for software copyright registration from a real software project.
iflytek-contract-intelligence-review
A contract-review workflow for scanned or digital agreements. It can recognize document text, examine clauses, detect risks, check compliance, and create translation summaries; its output is for review and is not formal legal advice.
legal-writer
Legal document drafting -- contracts, memos, briefs, complaints, demand letters, opinions, discovery, settlements, ToS, privacy policies. Full pipeline: document structure, per-section writing, Bluebook citation, case law lookup (CourtListener API), regulation lookup (eCFR API), DOCX output, and TDD-style verification…