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/sapientpants/deepsource-mcp-server/implement-github-issuegit clone --depth 1 https://github.com/sapientpants/deepsource-mcp-serverWhat 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.00863 |
| Opus 5 | $0.00000 | $0.00432 |
| Sonnet 5 | $0.00000 | $0.00173 |
| Haiku 4.5 | $0.00000 | $0.00086 |
Grade A, and why
implement-github-issue 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 yesterday.
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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement GitHub Issue
You are about to implement GitHub issue: $ARGUMENTS
Implementation Workflow
1. Analyze the Issue
gh issue view $ARGUMENTS
- Review the full issue description
- If it contains Gherkin specs, parse acceptance criteria carefully
- Identify non-goals and constraints
- Note any technical requirements
2. Research Codebase
- Search for relevant existing code
- Identify files needing modification
- Look for similar patterns to maintain consistency
- Review existing tests for patterns
3. Plan Implementation
Create a plan with:
- Core functionality breakdown
- Test strategy (unit + property-based)
- Files to create/modify
- Edge cases and risks
4. Create Feature Branch
# Follow branch naming from CLAUDE.md
git checkout -b <type>/<issue-number>-<description>
# Example: feat/42-user-authentication
5. Implement Solution
- Follow patterns in CLAUDE.md (validation, testing, imports)
- Write clean, focused functions
- Add TypeScript types and Zod validation
- Document public APIs with JSDoc
6. Write Tests
Required test coverage:
- Unit tests in
tests/*.spec.ts - Property-based tests in
tests/*.property.spec.tsfor business logic - Test both success and failure cases
- Verify edge cases
7. Verify Quality
pnpm verify # Runs all checks
8. Create Changeset
Changeset Guidance for Features:
# For bug fixes
pnpm changeset
# Select: patch
# Message: "Fix: [brief description of what was fixed]"
# For new features
pnpm changeset
# Select: minor
# Message: "Add [feature name]: [brief description]"
# For breaking changes
pnpm changeset
# Select: major
# Message: "BREAKING: [what changed and migration required]"
# For non-code changes (docs, tests, refactoring)
pnpm changeset --empty
# Message: "Internal: [what was changed]"
Decision Guide:
- patch: Bug fixes, security patches, performance improvements
- minor: New features, new APIs, significant enhancements
- major: Breaking changes, API removals, incompatible updates
- --empty: Documentation, tests, CI/CD, internal refactoring
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.
- yesterday First seen · 166 lines · 0 tokens per session scan A 2bfe9a3c4c86
implement-github-issue is a command published in the GitHub repository sapientpants/deepsource-mcp-server (7 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 863 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
zooza-setup
One-time Zooza setup — teaches Claude your business vocabulary so it understands your terms in every future session.
velog
Velog MCP 툴을 사용해서 아래 요청을 처리해줘.
commit
Create a conventional commit with emoji prefix.
Manage email across Gmail accounts via gmail MCP.
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.