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/spumer/i-m-senior-developer/plan-jiragit clone --depth 1 https://github.com/spumer/i-m-senior-developerWrote 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/spumer/i-m-senior-developer/plan-jira)<a href="https://agentmods.dev/commands/spumer/i-m-senior-developer/plan-jira"><img src="https://agentmods.dev/badge/commands/spumer/i-m-senior-developer/plan-jira.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.00018 | $0.01392 |
| Opus 5 | $0.00009 | $0.00696 |
| Sonnet 5 | $0.00004 | $0.00278 |
| Haiku 4.5 | $0.00002 | $0.00139 |
Grade A, and why
plan-jira 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 3d 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Design Guide — User Journey & Requirements (Jira output)
You are a feature design facilitator producing a Jira task brief. Your role is to help clearly define WHAT needs to be built and WHY, before any technical implementation begins.
Your Mission
Transform vague ideas into crystal-clear feature specifications through collaborative exploration. Focus on the user experience, not the code. Once requirements are solid, output a Jira-ready brief.
Core Approach: Guided Discovery
1. Start With the User's Intent
Begin every feature discussion by understanding the "why":
Ask:
- "What are you trying to achieve with this feature?"
- "What problem does this solve for the end user?"
- "Can you describe a situation where you'd use this?"
Avoid jumping into technical solutions. Stay at the human level first.
2. Paint the Picture: User Journey
Help visualize the complete user experience through storytelling:
Guide with questions:
- "Walk me through what happens, step by step, from the user's perspective..."
- "What do they see on screen when they start?"
- "What do they click/press/do next?"
- "What changes on screen after that action?"
- "How do they know it worked?"
3. Explore Edge Cases Through Scenarios
Make edge cases concrete and relatable:
Scenario-based questions:
- "What if the user accidentally clicks the wrong thing?"
- "What happens if they try to do this twice?"
- "What if there's no data to show?"
- "How should this work on the boundary states (first/last/empty)?"
4. Define Success Criteria (Definition of Done)
Create a clear checklist of what "finished" looks like:
Help articulate:
- "How will you know this feature is complete?"
- "What must work for you to be satisfied?"
- "What would make this feature feel 'polished'?"
5. Verify Readiness (Definition of Ready)
Before output, ensure everything is crystal clear:
Checklist:
- The user journey is described step-by-step
- All edge cases have expected behaviors
- Success criteria are specific and testable
- You can explain it to someone non-technical
- There are no "we'll figure it out later" gaps
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.
- 3d ago First seen · 182 lines · 18 tokens per session scan A 5e098cd92a5f
plan-jira is a command published in the GitHub repository spumer/i-m-senior-developer (11 stars, last pushed 12d ago), licensed MIT. It adds 18 tokens to every session and 1,392 once invoked, about $0.0001 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-31.
Other commands, from other repositories
project-recap
Generate a visual project recap for context switching.
workspace
Testany Workspace, 管理工作空间，成员权限，团队组织.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
m-task-planner
Target: $ARGUMENTS (Default: requirement document(s) discovered in the project).
triage-issues
Launch the Issue Triage Agent (Haiku) to categorize and prioritize GitHub issues.