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/create-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.00008 | $0.00606 |
| Opus 5 | $0.00004 | $0.00303 |
| Sonnet 5 | $0.00002 | $0.00121 |
| Haiku 4.5 | $0.00001 | $0.00061 |
Grade A, and why
create-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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create or update PR with the following additional instructions: $ARGUMENTS
Context
- Current branch:
!git branch --show-current - Remote tracking:
!git status -sb - PR draft file exists:
!test -f PR.md && echo "Yes" || echo "No"
Your task
Create or update a GitHub pull request based on the content in PR.md file.
Steps
-
Verify prerequisites:
- Ensure
PR.mdfile exists - If not, suggest running
/draft-prfirst - Check current branch is not main/master
- Ensure
-
Verify branch is pushed:
- Check if current branch is pushed to remote
- If not pushed:
git push -u origin $(git branch --show-current)
-
Check for existing PR:
- Check if PR already exists:
gh pr list --head $(git branch --show-current) - Store PR number if exists
- Check if PR already exists:
-
Read PR.md content:
- Read the
PR.mdfile - First line is the title
- Remaining lines are the body
- Read the
-
Show PR content to user:
- Display the title and body from PR.md
- If updating existing PR, show what will change
- Ask for explicit user approval:
- For new PR: "Would you like to create this PR? (You can edit PR.md first if needed)"
- For update: "Would you like to update PR #XXX with this content? (You can edit PR.md first if needed)"
-
Wait for user approval:
- MUST get explicit "yes" or confirmation from user
- If user wants to edit, wait for them to finish
-
Create or update PR (only after approval):
- If creating new PR:
gh pr create --title "$(head -n1 PR.md)" --body "$(tail -n+2 PR.md)" - If updating existing PR:
gh pr edit [PR_NUMBER] --title "$(head -n1 PR.md)" --body "$(tail -n+2 PR.md)"
- If creating new PR:
-
Show result:
- Display the PR URL
- Confirm success
Important Notes
- NEVER create/update PR without explicit user approval
- Always show what will be created/updated before proceeding
- Remind user they can edit PR.md before approval
- If PR.md doesn't exist, guide user to run
/draft-prfirst - Ensure branch is pushed before creating PR
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 · 71 lines · 8 tokens per session scan A ed4c6623e755
create-pr is a command published in the GitHub repository nyatinte/ccexp (271 stars, last pushed 8d ago), licensed MIT. It adds 8 tokens to every session and 606 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
git
Git operations with intelligent commit messages and workflow optimization.
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.