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/dhar174/custom_github_copilot_agent_builder/adr-generatorgit clone --depth 1 https://github.com/dhar174/custom_github_copilot_agent_builderWhat 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.01485 |
| Opus 5 | $0.00013 | $0.00743 |
| Sonnet 5 | $0.00005 | $0.00297 |
| Haiku 4.5 | $0.00003 | $0.00148 |
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 yesterday.
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.
This is a copy
94% identical to ADR Generator — 10 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 233 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.
- yesterday First seen · 233 lines · 26 tokens per session scan A 9a745be3199a
ADR Generator is an agent published in the GitHub repository dhar174/custom_github_copilot_agent_builder (7 stars, last pushed 7mo ago), licensed MIT. It adds 26 tokens to every session and 1,485 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to ADR Generator, differing in 10 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.