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/howmanysmall/npm-registry-mcp/create-pull-requestgit clone --depth 1 https://github.com/howmanysmall/npm-registry-mcpWrote 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/howmanysmall/npm-registry-mcp/create-pull-request)<a href="https://agentmods.dev/commands/howmanysmall/npm-registry-mcp/create-pull-request"><img src="https://agentmods.dev/badge/commands/howmanysmall/npm-registry-mcp/create-pull-request.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.00007 | $0.00342 |
| Opus 5 | $0.00003 | $0.00171 |
| Sonnet 5 | $0.00001 | $0.00068 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
create-pull-request 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 5d 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.
This is a copy
88% identical to pr — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Create Pull Request
Create a pull request for the current branch using gh CLI.
Workflow
Current branch status: !git status
Recent commits: !git log --oneline -5
Arguments: $ARGUMENTS
Process:
-
Ensure Branch is Ready: !
git status- Commit all changes
- Push to remote:
git push origin [branch-name]
-
Create PR: Create a well-formatted pull request
Title: conventional commits format, like
feat(ecs): add entity-component-system coreDescription template:
<!-- Are there any relevant issues / PRs / mailing lists discussions? Please reference them here. --> ## References - [links to github issues referenced in commit messages] ## Summary [Brief description of changes] ## Test Plan - [ ] Tests pass - [ ] Manual testing completed -
Set Base Branch: Default to main unless specified otherwise
-
Link Issues: Reference related issues found in commit messages
Use gh CLI
- Check current branch and ensure it's pushed
- Use
gh pr createwith proper title and description - Set the base branch (default: main)
- Include relevant issue references if found in commit messages
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.
- 5d ago First seen · 66 lines · 7 tokens per session scan A caf0926bd61b
create-pull-request is a command published in the GitHub repository howmanysmall/npm-registry-mcp (3 stars, last pushed 6mo ago), licensed MIT. It adds 7 tokens to every session and 342 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to pr, differing in 6 lines, and is treated as a copy.
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.