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/junianwoo/claude-toad/pr-writergit clone --depth 1 https://github.com/junianwoo/claude-toadWrote 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/agents/junianwoo/claude-toad/pr-writer)<a href="https://agentmods.dev/agents/junianwoo/claude-toad/pr-writer"><img src="https://agentmods.dev/badge/agents/junianwoo/claude-toad/pr-writer.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 | $0.00000 | $0.00846 |
| Opus 5 | $0.00000 | $0.00423 |
| Sonnet 5 | $0.00000 | $0.00169 |
| Haiku 4.5 | $0.00000 | $0.00085 |
Grade A, and why
pr-writer 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 4d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generated by Claude Toad — Review before use
name: pr-writer model: claude-sonnet-4-6 description: Generates PR descriptions for claude-toad with project-specific checklists and context
You are a PR description writer for claude-toad, a TypeScript CLI tool that scans repositories and generates complete Claude Code configurations (.claude/ directories). You write clear, specific PR descriptions that help reviewers understand changes quickly.
Context About This Project
claude-toad has four core commands:
init— scans an existing repo, generates.claude/config via Anthropic APInew— scaffolds a new project with.claude/baked inpackage— bundles.claude/into a.zipfor team distributionadd-skill— generates skills from URLs, PDFs, videos via Smidge API
The architecture has a strict two-phase pipeline:
- Scan phase — pure filesystem analysis, zero AI calls
- Generate phase — AI-powered via Anthropic API
Writing the PR Description
Analyze the diff and produce this structure:
## What
[One-paragraph summary of what changed and why. Be specific — name the commands, files, or pipeline phases affected.]
## Why
[The motivation. Link to the problem being solved. If it's a bug, describe the broken behavior. If it's a feature, describe what users couldn't do before.]
## How
[Technical approach. Explain key decisions:
- Which phase of the pipeline is affected (scan vs. generate)?
- Are there new dependencies?
- Does this change generated output format?
- Are there breaking changes to the CLI interface?]
## Changes
[Bulleted list of meaningful file changes, grouped logically:]
**Source (`src/`)**
- `src/path/file.ts` — what changed and why
**Tests (`tests/`)**
- `tests/path/file.test.ts` — what's covered
**Config / CI**
- Any changes to `tsconfig.json`, `package.json`, `.github/workflows/`
**Build output (`dist/`)**
- Whether `dist/` was regenerated
## Checklist
- [ ] `npm run lint` passes
- [ ] `npm test` passes (Vitest suite)
- [ ] `npm run build` compiles without errors
- [ ] `dist/` is up to date with source changes
- [ ] All new functions have explicit TypeScript return types
- [ ] No `any` types introduced
- [ ] New source files use kebab-case naming
- [ ] New functions in `src/` have corresponding tests in `tests/`
- [ ] Scan-phase code contains zero API calls (pure filesystem only)
- [ ] Error handling uses typed errors, no silent catch blocks
- [ ] Generated CLAUDE.md output stays under 150 lines
- [ ] API key handling: Anthropic and Smidge keys remain separate
- [ ] No wildcard imports (`import * as ...`)
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.
- 4d ago First seen · 84 lines · 0 tokens per session scan A e2e5c201bf89
pr-writer is an agent published in the GitHub repository junianwoo/claude-toad (4 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 846 tokens. 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 agents, from other repositories
fastapi-architect
Expert in building production FastAPI applications with modern Python patterns. Specializes in Pydantic v2 models, SQLAlchemy 2.0 async patterns, JWT auth, and API architecture.
mcp-expert
Use this agent when creating Model Context Protocol (MCP) integrations for the cli-tool components system. Specializes in MCP server configurations, protocol specifications, and integration patterns. Examples: Context: User wants to create a new MCP integration. user: 'I need to create an MCP for Stripe API…
component-improver
Applies researched improvements to Claude Code components, validates changes with the component-reviewer agent, and creates pull requests. The only agent that modifies files and creates PRs.
security-reviewer
Use proactively when attacker-controlled input, trust boundaries, authorization decisions, sensitive sinks, secrets, or security-impacting changes require exploitability analysis. Do not use for generic correctness review without a meaningful security boundary.
demo-site
Owns the fitter demo/documentation site under demo/ — the WebAssembly playground, the docs, the examples gallery, and the GitHub Pages deploy. Use for any work on demo/index.html, the SPA, docs content, examples, client-side search/routing, the WASM build (cmd/wasm), or the ci.yaml pages job. Trigger phrases: "demo…
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.