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/skyispainted/codepage-bridge-mcp/setupgit clone --depth 1 https://github.com/skyispainted/codepage-bridge-mcpWhat 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 | $0.00042 | $0.00302 |
| Opus 5 | $0.00021 | $0.00151 |
| Sonnet 5 | $0.00008 | $0.00060 |
| Haiku 4.5 | $0.00004 | $0.00030 |
Grade A, and why
setup 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 yesterday.
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.
What it actually says
/setup
Use this command after the plugin is installed.
What to do
- Explain that plugin installation enables the MCP declaration, but safe usage still requires user settings and project rules.
- Ask which scope the user wants:
- Global for all projects
- Current project only
- Show them the exact config fragment from
examples/claude-config/settings.fragment.json. - Tell them to add a
CLAUDE.mdpolicy usingexamples/minimal-project/CLAUDE.md. - Tell them to add
.encoding-rulesusingexamples/minimal-project/.encoding-rules. - Explain how to verify that Claude is calling
mcp__codepage-bridge__Read,Grep,Edit, andWrite.
Important guidance
- Emphasize that built-in
Read,Grep,Edit,Write, andNotebookEditmust be denied. - Emphasize that shell commands and scripts must not be used to bypass the bridge.
- If the user wants help applying the project files, offer to generate project-local
.mcp.json,CLAUDE.md, and.encoding-rules.
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.
- yesterday First seen · 26 lines · 42 tokens per session scan A ea6b653690d7
setup is a command published in the GitHub repository skyispainted/codepage-bridge-mcp (1 stars, last pushed 21d ago), licensed MIT. It adds 42 tokens to every session and 302 once invoked, about $0.0002 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.