the-commons: Command for Claude Code

.claude/commands/bug-fix.md

bug-fix is a command for Claude Code from mereditharmcgee/the-commons. It costs 0 tokens per session (1,507 once invoked), scanned A, original, MIT.

A bug-fixing mode for The Commons, an online space referenced by the add-on.

In plain words
What is it for?
Use it when a user reports a problem in The Commons and asks for the cause to be found, fixed, and checked.
Why use it?
The input only says that it handles a reported issue; it does not describe specific debugging methods or supported systems.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is mereditharmcgee/the-commons's own configuration. It tells Claude Code how to work on the-commons 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 the-commons configures →

Reuse

Borrowing it

Nothing to install: this file belongs to mereditharmcgee/the-commons. 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/mereditharmcgee/the-commons/main/.claude/commands/bug-fix.md
Clone the repo
git clone --depth 1 https://github.com/mereditharmcgee/the-commons

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/mereditharmcgee/the-commons/bug-fix/github.svg)](https://agentmods.dev/commands/mereditharmcgee/the-commons/bug-fix)
Your own site
<a href="https://agentmods.dev/commands/mereditharmcgee/the-commons/bug-fix"><img src="https://agentmods.dev/badge/commands/mereditharmcgee/the-commons/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.

agentmods 80×15 button for bug-fix

Your own site · 80×15
<a href="https://agentmods.dev/commands/mereditharmcgee/the-commons/bug-fix"><img src="https://agentmods.dev/badge/commands/mereditharmcgee/the-commons/bug-fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,507 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 original 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.00000 $0.01507
Opus 5.5 $0.00000 $0.00603
Sonnet 5.5 $0.00000 $0.00301
Haiku 4.5 $0.00000 $0.00151

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

Security

Grade A, and why

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 1mo 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/bug-fix.md · 138 lines

How it starts

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

Bug Fix Mode

You are entering bug fix mode for The Commons (jointhecommons.space). A user has reported an issue. Your job is to find the root cause, fix it, and verify the fix.

The Report

$ARGUMENTS


Architecture (Quick Reference)

  • Frontend: Static HTML/CSS/JS, no framework, no build step
  • Backend: Supabase PostgreSQL with Row Level Security (RLS)
  • Hosting: GitHub Pages at jointhecommons.space
  • Repo: C:\Users\mmcge\the-commons
  • Supabase project: dfephsfberzadihcrhal
  • Key config: js/config.js (API URL, anon key, endpoints)
  • Shared utilities: js/utils.js (API helpers, formatting, DOM helpers)
  • Auth system: js/auth.js (Supabase Auth, identity management)
  • Styles: css/style.css (single file, CSS custom properties)
  • SQL schemas: sql/schema/ directory (01-schema.sql through 10-user-post-management.sql)

Debugging Procedure

Follow these steps in order. Do not skip ahead.

Step 1: Understand the Report

Read the issue carefully. Identify:

  • What page is affected? (e.g., discussions.html, chat.html, postcards.html)
  • What behavior is wrong? (error, missing data, broken UI, wrong output)
  • What behavior is expected?
  • Is it reproducible? (always, sometimes, specific conditions)

State your understanding of the issue before proceeding.

Step 2: Identify the Relevant Files

Based on the affected page, read the relevant files. The mapping:

Page HTML JS SQL Schema
Home index.html js/home.js —
Discussions list discussions.html js/discussions.js sql/schema/01-schema.sql
Single discussion discussion.html js/discussion.js sql/schema/01-schema.sql
Submit response submit.html js/submit.js sql/schema/01-schema.sql
Propose question propose.html js/propose.js sql/schema/01-schema.sql
Reading Room reading-room.html js/reading-room.js sql/schema/06-reading-room-schema.sql
Single text text.html js/text.js sql/schema/06-reading-room-schema.sql
Postcards postcards.html js/postcards.js sql/schema/07-postcards-schema.sql
Gathering (chat) chat.html js/chat.js sql/schema/04-chat-schema.sql
Voices voices.html js/voices.js sql/schema/02-identity-system.sql
Profile profile.html js/profile.js sql/schema/02-identity-system.sql
Dashboard dashboard.html js/dashboard.js sql/schema/02-identity-system.sql
Login login.html js/auth.js sql/schema/02-identity-system.sql
Admin admin.html js/admin.js sql/admin/admin-rls-setup.sql
Moments moments.html js/moments.js sql/schema/05-moments-schema.sql

Read the full file on GitHub · 138 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.

  1. 1mo ago First seen · 138 lines · 0 tokens per session scan A 08f5b570d0be

Subscribe to this mod's changes

bug-fix is a command published in the GitHub repository mereditharmcgee/the-commons (3 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,507 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.