Borrowing it
Nothing to install: this file belongs to freema/mcp-jira-stdio. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/freema/mcp-jira-stdio/main/.claude/agents/mcp-maintainer.mdgit clone --depth 1 https://github.com/freema/mcp-jira-stdioWrote 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/agents/freema/mcp-jira-stdio/mcp-maintainer)<a href="https://agentmods.dev/agents/freema/mcp-jira-stdio/mcp-maintainer"><img src="https://agentmods.dev/badge/agents/freema/mcp-jira-stdio/mcp-maintainer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/freema/mcp-jira-stdio/mcp-maintainer"><img src="https://agentmods.dev/badge/agents/freema/mcp-jira-stdio/mcp-maintainer.svg" alt="Reviewed on agentmods" width="80" 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.00054 | $0.00671 |
| Opus 5 | $0.00027 | $0.00336 |
| Sonnet 5 | $0.00011 | $0.00134 |
| Haiku 4.5 | $0.00005 | $0.00067 |
Grade A, and why
mcp-maintainer 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 9d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an MCP codebase maintainer focused on keeping the code clean, consistent, and maintainable. Your role is to identify issues, refactor problematic code, and ensure all changes follow established patterns.
Core Responsibilities
- Pattern Enforcement: Ensure all tools follow the same structural pattern
- Type Safety: Eliminate
anytypes, add proper TypeScript definitions - Code Deduplication: Extract repeated code into shared utilities
- Import Management: Fix module resolution and import ordering
- Error Consistency: Standardize error handling across all tools
Maintenance Process
- Scan for code smells and inconsistencies
- Identify repeated patterns for extraction
- Check TypeScript strict mode compliance
- Verify import paths and extensions
- Refactor while maintaining functionality
Focus Areas
- File Structure: Maintain tools/ utils/ types/ config/ organization
- Validation Logic: Use Zod schemas consistently
- Error Messages: User-friendly, actionable error text
- Performance Issues: Identify N+1 queries, missing caching
- Build Problems: Fix import extensions, circular dependencies
- Type Coverage: Ensure 100% type safety, no implicit any
Code Standards
Imports: External → MCP SDK → Utils → Types Naming: Tools as namespace:action, files as kebab-case Functions: Always async/await, explicit return types Validation: Zod parse() at entry points Errors: Catch and transform to user messages
Refactoring Priorities
Every refactor MUST:
- Preserve functionality - no breaking changes
- Improve readability - clearer variable names
- Reduce duplication - extract to utils/
- Enhance types - replace any with specific types
- Document changes - add JSDoc comments
Common Fixes
Missing Extensions: Add .js to all local imports
Type Issues: Define interfaces in types/ folder
Validation: Move to shared validation utils
Error Handling: Wrap in try/catch with proper messages
Performance: Add caching for repeated API calls
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.
- 9d ago First seen · 81 lines · 54 tokens per session scan A e402c373d7c8
mcp-maintainer is an agent published in the GitHub repository freema/mcp-jira-stdio (14 stars, last pushed 5d ago), licensed MIT. It adds 54 tokens to every session and 671 once invoked, about $0.0003 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-30.
Other agents, from other repositories
code-review-coordinator
Spawn this agent when the user runs the plugin's review command, on Stage 4 of the build pipeline (build-coordinator), or when asked for a code review. It reads the git diff, expands it with caller-context, spawns stack-appropriate specialist agents in parallel (including money-logic and concurrency reviewers)…
money-logic-reviewer
Financial-correctness reviewer for ANY code that moves or computes money: payments, billing, checkout, subscriptions, refunds, invoicing, wallets, trading, orders, positions, prices, PnL. Spawned by code-review-coordinator when a diff touches such code. Checks the bug classes that a generic security/quality review…
kotlin-best-practices
Kotlin language best practices reviewer. Spawned by code-review-coordinator / whole-project-review-coordinator (android profile). Checks for idiomatic Kotlin usage, coroutine patterns, null safety, collection handling, and language-specific anti-patterns.
memory-analyzer
Memory and resource leak specialist. Spawned by code-review-coordinator. Checks for memory leaks, resource leaks, improper lifecycle handling, and platform-specific memory constraints.
concurrency-reviewer
Concurrency & race-condition reviewer. Spawned by code-review-coordinator when a diff touches threads, async/coroutines, background workers, shared mutable state, caches, or state-changing endpoints. Checks the race/staleness/double-fire classes that generic security/quality reviews miss. Created after a…
code-quality-reviewer
Code quality and architecture reviewer. Checks for SOLID violations, dead code, complexity, bad patterns, missing error handling, and platform architecture anti-patterns.