gem-jira-mcp: Command for Claude Code

.claude/commands/update-docs.md

update-docs is a command for Claude Code from namcpgem/gem-jira-mcp. It costs 23 tokens per session (75 once invoked), scanned A, original, no licence file.

A command that updates README.md and Markdown files in the docs/ folder to match the source code.

In plain words
What is it for?
Synchronising the project README and documentation files with the current source code.
Why use it?
It helps keep written documentation aligned with code changes.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is namcpgem/gem-jira-mcp's own configuration. It tells Claude Code how to work on gem-jira-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything gem-jira-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to namcpgem/gem-jira-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/namcpgem/gem-jira-mcp/main/.claude/commands/update-docs.md
Clone the repo
git clone --depth 1 https://github.com/namcpgem/gem-jira-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for update-docs

README.md
[![agentmods](https://agentmods.dev/badge/commands/namcpgem/gem-jira-mcp/update-docs/github.svg)](https://agentmods.dev/commands/namcpgem/gem-jira-mcp/update-docs)
Your own site
<a href="https://agentmods.dev/commands/namcpgem/gem-jira-mcp/update-docs"><img src="https://agentmods.dev/badge/commands/namcpgem/gem-jira-mcp/update-docs/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.

agentmods 80×15 button for update-docs

Your own site · 80×15
<a href="https://agentmods.dev/commands/namcpgem/gem-jira-mcp/update-docs"><img src="https://agentmods.dev/badge/commands/namcpgem/gem-jira-mcp/update-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 75 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00023 $0.00075
Opus 5.5 $0.00009 $0.00030
Sonnet 5.5 $0.00005 $0.00015
Haiku 4.5 $0.00002 $0.00007

Measured 2mo ago against content hash 9b5a443eb118, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

update-docs 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 2mo 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.

.claude/commands/update-docs.md · 7 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Changes

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.

  1. 2mo ago First seen · 7 lines · 23 tokens per session scan A 9b5a443eb118

Subscribe to this mod's changes

update-docs is a command published in the GitHub repository namcpgem/gem-jira-mcp (2 stars, last pushed 15d ago), with no licence file. It adds 23 tokens to every session and 75 once invoked, about $0.0001 per session on Opus 5.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.

Related

update-docs compared with commands from other repositories

update-docs next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
update-docsnamcpgem/gem-jira-mcpCommand215d agononeA23Claude Code
checklistgithub/spec-kitCommand148ktodayMITA13Claude Code
clarifygithub/spec-kitCommand148ktodayMITA27Claude Code
specifygithub/spec-kitCommand148ktodayMITA13Claude Code
convergegithub/spec-kitCommand148ktodayMITA35Claude Code
speckit.bug.testgithub/spec-kitCommand148ktodayMITA13Claude Code
analyzegithub/spec-kitCommand148ktodayMITA26Claude Code