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/carlwestman/borsdata-mcp-server/next-issuegit clone --depth 1 https://github.com/carlwestman/borsdata-mcp-serverWrote 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/carlwestman/borsdata-mcp-server/next-issue)<a href="https://agentmods.dev/commands/carlwestman/borsdata-mcp-server/next-issue"><img src="https://agentmods.dev/badge/commands/carlwestman/borsdata-mcp-server/next-issue.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 | $0.00000 | $0.00451 |
| Opus 5 | $0.00000 | $0.00226 |
| Sonnet 5 | $0.00000 | $0.00090 |
| Haiku 4.5 | $0.00000 | $0.00045 |
Grade A, and why
next-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 4d 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.
What it actually says
/next-issue — Pick up the next issue from the project board
You are picking up the next prioritised issue from the GitHub Project board.
Steps
-
Get the next issue by running:
./scripts/gh-project.sh nextThis returns the top item in the "Ready" column (highest priority).
-
If no items are in Ready, inform me and stop.
-
Read the full issue including all comments for additional context:
gh issue view <NUMBER> --repo $GH_PROJECT_OWNER/$GH_PROJECT_REPO --comments -
Move the issue to In Progress:
./scripts/gh-project.sh move <NUMBER> "In Progress" -
Create a working branch:
git checkout -b issue-<NUMBER>-<short-slug> mainUse a short kebab-case slug derived from the issue title.
-
Add a progress header to the issue description so the team can see work has started:
gh issue edit <NUMBER> --body "$(gh issue view <NUMBER> --json body -q .body) --- ## 🔧 Implementation Progress - ⏳ Started: $(date -u +%Y-%m-%dT%H:%M:%SZ) - Branch: \`issue-<NUMBER>-<slug>\` - Status: **In Progress** " -
Start implementing. Read any referenced files, specs, or docs mentioned in the issue. Follow the project's existing patterns and conventions. Refer to
/docsandCLAUDE.mdfor project rules. -
Update the issue description periodically as you complete meaningful steps — append bullet points under the Implementation Progress section describing what was done.
Rules
- Never force-push to main.
- Always work on a feature branch.
- Run existing tests before considering the work complete.
- If the issue is unclear or blocked, add a comment to the issue asking for clarification and let me know.
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.
- 4d ago First seen · 52 lines · 0 tokens per session scan A c9dab260f01c
next-issue is a command published in the GitHub repository carlwestman/borsdata-mcp-server (0 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 451 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
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.