What is speckit-bug-fix?

A bug-fixing workflow that applies a previously proposed remedy and saves a report of the changes. It only works when a bug assessment already exists.

Use it to fix a named bug, find the relevant assessment when possible, and write the result to a bug-specific fix report.

It keeps the fix tied to an earlier assessment and leaves a written record, so developers do not have to repeat the investigation or guess what changed.

How karenrebecag/analytics-mcp configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to karenrebecag/analytics-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/karenrebecag/analytics-mcp/main/.claude/skills/speckit-bug-fix/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/karenrebecag/analytics-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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/karenrebecag/analytics-mcp/speckit-bug-fix/github.svg)](https://agentmods.dev/skills/karenrebecag/analytics-mcp/speckit-bug-fix)

Your own site

<a href="https://agentmods.dev/skills/karenrebecag/analytics-mcp/speckit-bug-fix"><img src="https://agentmods.dev/badge/skills/karenrebecag/analytics-mcp/speckit-bug-fix/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/karenrebecag/analytics-mcp/speckit-bug-fix"><img src="https://agentmods.dev/badge/skills/karenrebecag/analytics-mcp/speckit-bug-fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,325 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 98% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5.1	$0.00020	$0.01325
Opus 5.5	$0.00008	$0.00530
Sonnet 5.5	$0.00004	$0.00265
Haiku 4.5	$0.00002	$0.00133

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

Security

Grade A, and why

speckit-bug-fix 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.

Origin

This is a copy

98% identical to speckit-bug-fix — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/skills/speckit-bug-fix/SKILL.md · 117 lines

How it starts

The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Fix Bug

Apply the remediation that was proposed by /speckit-bug-assess and record the changes in a fix report at .specify/bugs/<slug>/fix.md. This command is only valid after an assessment exists for the given slug.

User Input

$ARGUMENTS

The user input should identify the bug to fix. Accept any of:

slug=<bug-slug> or --slug <bug-slug> or just a bare slug-like token.
A path that contains the slug (e.g. .specify/bugs/login-timeout/).
Nothing — fall back to context (see below).

Slug Resolution

Resolve BUG_SLUG in this order, stopping at the first match:

Explicit user input — a slug passed in $ARGUMENTS (any of the forms above).
Conversation context — if the current session has just run /speckit-bug-assess, the slug it reported is the working slug. Reuse it without re-prompting. Confirm it by checking that .specify/bugs/<slug>/assessment.md exists; if it does not, fall through.
Single candidate on disk — list .specify/bugs/*/assessment.md. If exactly one matching assessment.md is found, use the slug from its parent directory.
Disambiguate:
- Interactive mode: ask the user which bug to fix and list the candidates.
- Automated mode: stop with an error listing the candidates. Do not guess.

Once resolved, set BUG_SLUG and BUG_DIR = .specify/bugs/<BUG_SLUG>, and briefly state in your reply which resolution path was used (explicit / from context / single candidate / asked).

Prerequisites

BUG_DIR/assessment.md MUST exist. If it does not, stop and instruct the user to run /speckit-bug-assess first.
If BUG_DIR/fix.md already exists, ask the user whether to overwrite it before continuing (interactive mode) or refuse (automated mode).
Read BUG_DIR/assessment.md in full. Treat its Proposed Remediation, Files likely to change, Tests to add or update, and Risks & Considerations sections as the contract for this command.

Execution

Confirm the plan
- Restate, in 3–6 bullets, what you are about to change and where, based on the assessment.
- If the assessment's verdict is invalid, stop — there is nothing to fix. Tell the user and exit.
- If the verdict is likely valid, needs reproduction and there are unresolved [NEEDS CLARIFICATION] items, flag them and ask the user whether to proceed in interactive mode, or stop in automated mode.

Read the full file on GitHub · 117 lines

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.

2mo ago First seen · 117 lines · 20 tokens per session scan A 93d7302cd3bf

Subscribe to this mod's changes

speckit-bug-fix is a skill published in the GitHub repository karenrebecag/analytics-mcp (1 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 1,325 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 98% identical to speckit-bug-fix, differing in 2 lines, and is treated as a copy.

Analytics and metrics Debugging ai-tools claude cloudflare-analytics ga4 google-analytics

speckit-bug-fix next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
speckit-bug-fixkarenrebecag/analytics-mcp	Skill	1	1mo ago	MIT	A	20	Claude Code
traffic-diagnosissurendranb/google-analytics-mcp	Skill	244	5d ago	MIT	A	34	Claude Code
opencli-autofixjackwener/OpenCLI	Skill	31k	yesterday	Apache-2.0	A	61	Claude Code
omh-live-incident-responserlaope/oh-my-hermes	Skill	5.2k	yesterday	MIT	A	87	Claude Code, Codex
omh-failure-signal-auditrlaope/oh-my-hermes	Skill	5.2k	yesterday	MIT	A	75	Claude Code, Codex
report-issue-localcyanheads/obsidian-mcp-server	Skill	702	7d ago	Apache-2.0	A	44	Claude Code
debuggingWrongStack/WrongStack	Skill	404	yesterday	MIT	A	175	Claude Code, Codex

analytics-mcp: Skill for Claude Code