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 commands/nyatinte/ccexp/draft-prgit clone --depth 1 https://github.com/nyatinte/ccexpWhat 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.00009 | $0.00581 |
| Opus 5 | $0.00005 | $0.00291 |
| Sonnet 5 | $0.00002 | $0.00116 |
| Haiku 4.5 | $0.00001 | $0.00058 |
Grade A, and why
draft-pr 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.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Draft PR content with the following additional instructions: $ARGUMENTS
Context
- Current branch:
!git branch --show-current - Remote tracking:
!git status -sb - Recent commits on this branch:
!git log origin/main..HEAD --oneline - Repository info:
!gh repo view --json owner,name
Your task
Create a PR draft in PR.md file based on the current branch changes.
Steps
-
Verify branch status:
- Ensure current branch is not main/master
- Check if there are commits to create PR for
- If no commits or on main branch, inform user and exit
-
Check for existing PR:
- Check if PR already exists:
gh pr list --head $(git branch --show-current) - If PR exists, get current PR details for comparison
- Check if PR already exists:
-
Analyze repository PR style:
- Search for past PRs:
gh pr list --state merged --limit 10 - Analyze recent PRs for:
- Title format and language
- Description structure
- Common patterns
- Search for past PRs:
-
Load PR template:
- Read
.github/PULL_REQUEST_TEMPLATE.mdif it exists - Use template structure as base
- Read
-
Analyze changes:
- Get all commit messages:
git log origin/main..HEAD --pretty=format:"%s" - Get detailed diff if needed:
git diff origin/main..HEAD --stat - Understand the overall purpose of changes
- Get all commit messages:
-
Create PR.md file:
- Follow the template structure (Summary, Why, Changes with AS-IS/TO-BE)
- Write clear title (first line)
- Write comprehensive description (rest of file)
- Match the repository's PR language and style
- Include all relevant context
-
Show draft to user:
- Display the created
PR.mdcontent - Inform user they can edit
PR.mdbefore creating the PR - Suggest using
/create-prcommand next
- Display the created
Important Notes
- DO NOT create the actual PR - only draft the content in PR.md
- Follow the repository's existing PR style and language
- Ensure PR.md follows the template format (Summary/Why/Changes)
- Make the description comprehensive but concise
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 · 66 lines · 9 tokens per session scan A f311cd92e824
draft-pr is a command published in the GitHub repository nyatinte/ccexp (271 stars, last pushed 7d ago), licensed MIT. It adds 9 tokens to every session and 581 once invoked, about $0.0000 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.