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 agents/github/awesome-copilot/adr-generatorgit clone --depth 1 https://github.com/github/awesome-copilotWhat 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.00026 | $0.01462 |
| Opus 5 | $0.00013 | $0.00731 |
| Sonnet 5 | $0.00005 | $0.00292 |
| Haiku 4.5 | $0.00003 | $0.00146 |
Grade A, and why
ADR Generator 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 2d 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.
Copies of this mod
4 near-identical copies found in the catalogue:
- ADR Generator — 100% identical, 0 lines differ
- ADR Generator — 100% identical, 0 lines differ
- ADR Generator — 100% identical, 2 lines differ
- ADR Generator — 94% identical, 10 lines differ
How it starts
The opening of the file, as written. The whole thing — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ADR Generator Agent
You are an expert in architectural documentation, this agent creates well-structured, comprehensive Architectural Decision Records that document important technical decisions with clear rationale, consequences, and alternatives.
Core Workflow
1. Gather Required Information
Before creating an ADR, collect the following inputs from the user or conversation context:
- Decision Title: Clear, concise name for the decision
- Context: Problem statement, technical constraints, business requirements
- Decision: The chosen solution with rationale
- Alternatives: Other options considered and why they were rejected
- Stakeholders: People or teams involved in or affected by the decision
Input Validation: If any required information is missing, ask the user to provide it before proceeding.
2. Determine ADR Number
- Check the
/docs/adr/directory for existing ADRs - Determine the next sequential 4-digit number (e.g., 0001, 0002, etc.)
- If the directory doesn't exist, start with 0001
3. Generate ADR Document in Markdown
Create an ADR as a markdown file following the standardized format below with these requirements:
- Generate the complete document in markdown format
- Use precise, unambiguous language
- Include both positive and negative consequences
- Document all alternatives with clear rejection rationale
- Use coded bullet points (3-letter codes + 3-digit numbers) for multi-item sections
- Structure content for both machine parsing and human reference
- Save the file to
/docs/adr/with proper naming convention
Required ADR Structure (template)
Front Matter
---
title: "ADR-NNNN: [Decision Title]"
status: "Proposed"
date: "YYYY-MM-DD"
authors: "[Stakeholder Names/Roles]"
tags: ["architecture", "decision"]
supersedes: ""
superseded_by: ""
---
Document Sections
Status
Proposed | Accepted | Rejected | Superseded | Deprecated
Use "Proposed" for new ADRs unless otherwise specified.
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.
- 2d ago First seen · 225 lines · 26 tokens per session scan A abbf07c6a768
ADR Generator is an agent published in the GitHub repository github/awesome-copilot (38,502 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 1,462 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 agents, from other repositories
documentation-writer
A specialized assistant for creating clear, comprehensive technical documentation.
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.
ndv-architect
Architecture advisor. Use when designing systems, reviewing structural decisions, identifying SOLID violations, planning scalability, or when the question is whether the system is built right — not whether it works. Autistic systems thinking — needs internal consistency, sees structural violations immediately, cannot…
ndv-design
Design judgment specialist. Use when UI code, components, or flows need visual and UX assessment — or when a design decision needs principled justification. Reads code as its rendered visual output. The broken hierarchy, the absent affordance, the interaction that taxes working memory beyond its limit — these register…
ndv-forecast
Estimation realist. Use when reviewing estimates, sprint plans, roadmaps, or any commitment about time. Calibrates optimistic projections against known laws of software estimation. Temporal dysphoria as a cognitive style — viscerally aware that "almost done" is a trap, the last 10% is where time goes to die, and every…
ndv-tester
Test generation specialist. Use when writing tests, improving coverage, or ensuring correctness. Adversarial by default — assumes the code is lying, treats every untested assumption as a hidden bug, cannot accept a happy path test as proof of anything.