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 skills add marcusrbrown/systematic --skill report-bug-cegit clone --depth 1 https://github.com/marcusrbrown/systematicWrote 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/skills/marcusrbrown/systematic/report-bug-ce)<a href="https://agentmods.dev/skills/marcusrbrown/systematic/report-bug-ce"><img src="https://agentmods.dev/badge/skills/marcusrbrown/systematic/report-bug-ce/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/skills/marcusrbrown/systematic/report-bug-ce"><img src="https://agentmods.dev/badge/skills/marcusrbrown/systematic/report-bug-ce.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.00040 | $0.01070 |
| Opus 5.5 | $0.00016 | $0.00428 |
| Sonnet 5.5 | $0.00008 | $0.00214 |
| Haiku 4.5 | $0.00004 | $0.00107 |
Grade A, and why
report-bug-ce 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.
This is a copy
86% identical to report-bug-ce — 32 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.
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Report a Systematic Plugin Bug
Report bugs encountered while using the Systematic plugin. This skill gathers structured information and creates a GitHub issue for maintainers.
Step 1: Gather Bug Information
Ask the user the following questions (using the platform's blocking question tool — e.g., question in OpenCode, request_user_input in Codex, ask_user in Gemini; in Pi, use the blocking-question extension if available, otherwise present numbered options in chat and wait — or present numbered options and wait for a reply):
Question 1: Bug Category
- What type of issue are you experiencing?
- Options: Agent not working, Command not working, Skill not working, MCP server issue, Installation problem, Other
Question 2: Specific Component
- Which specific component is affected?
- Ask for the name of the agent, command, skill, or MCP server
Question 3: What Happened (Actual Behavior)
- Ask: "What happened when you used this component?"
- Get a clear description of the actual behavior
Question 4: What Should Have Happened (Expected Behavior)
- Ask: "What did you expect to happen instead?"
- Get a clear description of expected behavior
Question 5: Steps to Reproduce
- Ask: "What steps did you take before the bug occurred?"
- Get reproduction steps
Question 6: Error Messages
- Ask: "Did you see any error messages? If so, please share them."
- Capture any error output
Step 2: Collect Environment Information
Automatically gather environment details. Detect the coding agent platform and collect what is available:
OS info (all platforms):
uname -a
Plugin version: Read the plugin manifest or installed plugin metadata. Common locations:
- OpenCode:
~/.config/opencode/plugins/installed_plugins.json - Codex:
.codex/plugins/or project config - Other platforms: check the platform's plugin registry
Agent CLI version: Run the platform's version command:
- OpenCode:
opencode --version - Codex:
codex --version - Other platforms: use the appropriate CLI version flag
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.
- 1mo ago First seen · 158 lines · 40 tokens per session scan A bb1c43e616e0
report-bug-ce is a skill published in the GitHub repository marcusrbrown/systematic (25 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 1,070 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to report-bug-ce, differing in 32 lines, and is treated as a copy.
Other skills, from other repositories
ai-slop-cleaner
Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode.
smiles-validation
Strict SMILES validation, structural comparison, and modification verification. Catches invalid LLM-generated molecules.
kimaki-debug
Debug and administer Kimaki itself. Use when sessions do not respond, the bot shows errors, you need the Kimaki or OpenCode service logs, want to profile the bot, restart it (only when asked), connect a model provider with kimaki login, check who may use the bot, or file a Kimaki bug report. ALWAYS load when Kimaki…
lcx-report-bug
Create a high-signal bug issue or PR in the repo that owns the defect. Use this whenever the user asks to report, file, open, or triage a LazyCodex, lazycodex-ai, omo-codex, Codex plugin, or upstream Codex CLI bug, especially when they need source-backed root cause, reproduction steps, fix guidance, and GitHub routing.
remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits. Triggers: remove dead code, dead code, cleanup, remove unused.
confirm-failures-are-causally-linked-to-the-task-before-reportin
When delegating a task affected by this skill, include.