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.
git clone --depth 1 https://github.com/saajunaid/caddis-pluginWrote 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/commands/saajunaid/caddis-plugin/adr)<a href="https://agentmods.dev/commands/saajunaid/caddis-plugin/adr"><img src="https://agentmods.dev/badge/commands/saajunaid/caddis-plugin/adr/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/commands/saajunaid/caddis-plugin/adr"><img src="https://agentmods.dev/badge/commands/saajunaid/caddis-plugin/adr.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.00014 | $0.00694 |
| Opus 5.5 | $0.00006 | $0.00278 |
| Sonnet 5.5 | $0.00003 | $0.00139 |
| Haiku 4.5 | $0.00001 | $0.00069 |
Grade A, and why
adr 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 1mo 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Architectural Decision Record
Generate an ADR document for a technical decision using the standard ADR format.
Instructions
- If the decision title, context, or chosen approach is not clear from the conversation, ask before proceeding.
- Create the ADR file at
docs/adr/adr-NNNN-<title-slug>.md, whereNNNNis the next sequential number. - Apply
.github/instructions/document-frontmatter.instructions.mdwhen creating or updating the ADR. The YAML frontmatter block must be the first content in the file. New ADRs requireOriginal Author,Creation Date, andCreating Model; updated ADRs must preserve those fields and add or updateLast Author,Last Updated, andLast Model Used. - Follow the template below exactly. Fill in every section with clear, unambiguous language.
ADR Template
---
title: "ADR-NNNN: <Decision Title>"
status: "Proposed"
date: "<YYYY-MM-DDTHH:MM:SSZ>"
authors: "<author names or roles>"
tags: ["architecture", "decision"]
supersedes: ""
superseded_by: ""
Original Author: "<active author or agent name>"
Creation Date: "<YYYY-MM-DDTHH:MM:SSZ>"
Creating Model: "<exact runtime model identifier or display name>"
---
# ADR-NNNN: <Decision Title>
## Status
**Proposed** | Accepted | Rejected | Superseded | Deprecated
## Context
<Problem statement, technical constraints, business requirements, and environmental
factors that make this decision necessary. Be specific about what forces are at play.>
## Decision
<The chosen solution and the rationale for selecting it over the alternatives.>
## Consequences
### Positive
- <Beneficial outcome or advantage>
- <Performance, maintainability, or scalability improvement>
- <Alignment with architectural principles or team goals>
### Negative
- <Trade-off, limitation, or drawback>
- <Technical debt or added complexity>
- <Risk or future challenge>
## Alternatives Considered
### <Alternative 1 Name>
- **Description**: <Brief technical description>
- **Rejection Reason**: <Why this was not selected>
### <Alternative 2 Name>
- **Description**: <Brief technical description>
- **Rejection Reason**: <Why this was not selected>
## Implementation Notes
- <Key implementation considerations>
- <Migration or rollout strategy, if applicable>
- <Monitoring and success criteria>
## References
- <Related ADRs, external docs, or standards referenced>
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.
- 1mo ago First seen · 97 lines · 14 tokens per session scan A d07262e7157c
adr is a command published in the GitHub repository saajunaid/caddis-plugin (0 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 694 once invoked, about $0.0001 per session on Opus 5.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-09-09.
Other commands, from other repositories
multi-repo-swarm
Coordinate AI swarms across multiple repositories, enabling organization-wide automation and intelligent cross-project collaboration.
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
prototype
Command dispatcher for prototype.
specify
Command dispatcher for specify.
run-workflow
Validate and establish the proven rn-dev-agent operating sequence before a real React Native journey — declared package manager and dependencies, read-only inventory, typed session recovery, one exclusive device, managed integration and Metro, only the requested proof, reverse-order cleanup.
status
Show the current in-flight task state — active phase, plan, gate, sign-off progress, and next action. Read-only; writes nothing.