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/stolostron/jira-mcp-server/summarygit clone --depth 1 https://github.com/stolostron/jira-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/stolostron/jira-mcp-server/summary)<a href="https://agentmods.dev/commands/stolostron/jira-mcp-server/summary"><img src="https://agentmods.dev/badge/commands/stolostron/jira-mcp-server/summary.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.00000 | $0.00642 |
| Opus 5 | $0.00000 | $0.00321 |
| Sonnet 5 | $0.00000 | $0.00128 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
summary 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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Work Summary Command
Generate a formal summary of work performed in the current AI session, based on repository changes and conversation context.
Instructions
Step 1: Gather Repository Changes
Run the following git commands in parallel using Bash:
git diff --stat— Get a summary of changed filesgit diff— Get the full diff of all changesgit log --oneline -5— Get recent commits for contextgit branch --show-current— Get the current branch name
Step 2: Gather Session Context
Review the full conversation history to identify:
- Which Jira issues were referenced, created, updated, transitioned, or commented on
- What tasks were performed (code changes, bug fixes, new features, refactoring, etc.)
- Any decisions made or trade-offs discussed
- Any tools or MCP servers used
Step 3: Generate the Formal Work Summary
Present a Formal Work Summary in this format:
## Work Summary — <current date>
**Branch:** <branch name>
**Session scope:** <1-line description of overall work>
### Changes
- <bullet list of meaningful changes, grouped by area/file>
### Notes
- <any relevant decisions, trade-offs, or follow-ups>
Step 4: Generate Git Commit Message Version
Generate a plain-text version suitable for a git commit message:
- No markdown formatting, no special characters (no backticks, asterisks, pipes, or angle brackets)
- First line is a concise summary under 72 characters
- Followed by a blank line and bullet points describing the changes
- Use only ASCII characters, hyphens, and standard punctuation
- This message will be used directly in CLI commands (e.g.,
git commit -m), so avoid characters that interfere with shell interpretation (quotes, backticks, dollar signs, parentheses, etc.)
Present it in a code block labeled Git Commit Message.
Step 5: Offer to Add Summary to Jira
Use AskUserQuestion to ask the user:
"Would you like to add this summary as a comment to a Jira issue? If so, provide the issue key (e.g., ACM-12345)."
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 · 77 lines · 0 tokens per session scan A f3e611e4a7cf
summary is a command published in the GitHub repository stolostron/jira-mcp-server (2 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 642 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
cancel-ralph
Cancel active Ralph Loop.
obsidian-recap
Summarize a time period from the vault - today, week, or month.
setup-pm-skills
Onboard a new user — find out what they do, recommend the right bundles & top skills, and set up a project CONTEXT.md so every skill is tailored to them.
release
Perform a full release: generate release notes, bump version, commit, tag, and push.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
engage.actions
Execute Phase 7 - Actions on Objectives and Goal Achievement.