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 hmcts/agentic-plugins-marketplace --skill adr-templategit clone --depth 1 https://github.com/hmcts/agentic-plugins-marketplaceWrote 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/hmcts/agentic-plugins-marketplace/adr-template)<a href="https://agentmods.dev/skills/hmcts/agentic-plugins-marketplace/adr-template"><img src="https://agentmods.dev/badge/skills/hmcts/agentic-plugins-marketplace/adr-template.svg" alt="Measured on agentmods" 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.00033 | $0.00407 |
| Opus 5 | $0.00016 | $0.00204 |
| Sonnet 5 | $0.00007 | $0.00081 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
adr-template 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 7d 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.
What it actually says
ADR Template (Architecture Decision Record)
Purpose
Record a significant architectural, technology, or design decision. Creates a permanent, reviewable audit trail so a future engineer can understand — or reverse — the decision.
When to write an ADR
- Introducing a new dependency or framework
- Choosing between two viable architectural patterns
- Deviating from an existing tech stack or coding standard
- Making a security or data-handling decision with no clear prior precedent
- Any decision a future engineer would need context to understand or reverse
File naming
docs/adrs/NNN-short-title-in-kebab-case.md
NNN = three-digit sequence, starting from 001.
Template
# ADR-NNN: [Short title]
## Status
[Proposed | Accepted | Deprecated | Superseded by ADR-NNN]
## Date
[YYYY-MM-DD]
## Context
[What situation, constraint, or requirement prompted this decision?
What forces are at play? What is the problem being solved?]
## Decision
[What was decided? State it clearly and positively.
"We will use X" not "We considered X".]
## Options considered
| Option | Pros | Cons |
|--------|------|------|
| ... | ... | ... |
## Consequences
[What are the expected outcomes — positive and negative?
What does this make easier? What does it make harder?
Any follow-up actions or tickets created?]
## Compliance notes
[Any compliance or regulatory considerations relevant to this decision.]
Process
- Draft the ADR before implementing the decision
- Commit it to the feature branch alongside the code it describes
- Reference the ADR number in the PR description
- If the decision is significant, surface it for review before merge
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.
- 7d ago First seen · 61 lines · 33 tokens per session scan A 4df6315e931c
adr-template is a skill published in the GitHub repository hmcts/agentic-plugins-marketplace (3 stars, last pushed 2d ago), licensed MIT. It adds 33 tokens to every session and 407 once invoked, about $0.0002 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-31.
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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…