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/mort-lab/excel-mcp/create-prgit clone --depth 1 https://github.com/mort-lab/excel-mcpWhat 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.00493 |
| Opus 5 | $0.00000 | $0.00246 |
| Sonnet 5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00049 |
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- prp-core-pr — 100% identical, 0 lines differ
What it actually says
Create Pull Request
Create a well-structured pull request with proper description and context.
PR Title (if provided)
$ARGUMENTS
Process
-
Prepare Branch
# Check current branch git branch --show-current # Ensure we're not on main # If on main, create a feature branch -
Review Changes
# See what will be included git status git diff main...HEAD -
Create Commits
- Stage relevant files
- Create logical, atomic commits if not already done
- Write clear commit messages following conventional commits, do not include any reference to cluade, written by clade etc:
feat:for new featuresfix:for bug fixesdocs:for documentationtest:for testsrefactor:for refactoring
-
Push to Remote
git push -u origin HEAD -
Create PR
gh pr create --title "$ARGUMENTS" --body "$(cat <<'EOF' ## Summary [Brief description of what this PR does] ## Changes - [List key changes] - [Be specific] ## Type of Change - [ ] Bug fix - [ ] New feature - [ ] Breaking change - [ ] Documentation update ## Testing - [ ] Tests pass locally - [ ] Added new tests - [ ] Manual testing completed ## Checklist - [ ] Code follows project style - [ ] Self-reviewed - [ ] Updated documentation - [ ] No console.logs or debug code ## Screenshots (if applicable) [Add screenshots for UI changes] ## Additional Context [Any extra information reviewers should know] EOF )" -
Post-Creation
- Add labels if needed:
gh pr edit --add-label "feature,needs-review" - Request reviewers if known
- Link to related issues
- Add labels if needed:
Remember to:
- Keep PRs focused and small
- Provide context for reviewers
- Test thoroughly 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 · 85 lines · 0 tokens per session scan A d17c7ebf2353
create-pr is a command published in the GitHub repository mort-lab/excel-mcp (5 stars, last pushed 25d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 493 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 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.