Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/rajitsaha/100xprismnpx agentmods add skills/rajitsaha/100xprism/fix-bugsWrote 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/rajitsaha/100xprism/fix-bugs)<a href="https://agentmods.dev/skills/rajitsaha/100xprism/fix-bugs"><img src="https://agentmods.dev/badge/skills/rajitsaha/100xprism/fix-bugs.svg" alt="Measured on agentmods" 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.00051 | $0.01029 |
| Opus 5 | $0.00026 | $0.00515 |
| Sonnet 5 | $0.00010 | $0.00206 |
| Haiku 4.5 | $0.00005 | $0.00103 |
Grade A, and why
fix-bugs 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix — Autonomous Bug Fixer
Fix the bug described or linked. Investigate and fix without step-by-step guidance.
Do NOT ask for permission — investigate and fix autonomously.
How to use
/fix— fix the most recent failing CI run/fix <description>— fix from plain description/fix <docker logs paste>— trace error to root cause and fix/fix <Slack URL or paste>— read thread, extract bug report, fix
Phase 1 — Gather context
Read the error in full — message, stack trace, or thread. Do not skip this step.
If the root cause is not obvious from the error/stack/logs → invoke the
systematic-debugging skill first to diagnose before attempting any fix. /fix assumes
you know (or can quickly find) what's broken; for mysterious failures, diagnosis comes
first. Don't guess.
Detect the stack so context-gathering matches the project (canonical block — source:
_lib/reference.md):
PROJECT_ROOT=$(git rev-parse --show-toplevel); cd "$PROJECT_ROOT"
CI_SYSTEM=""; ls "$PROJECT_ROOT"/.github/workflows/*.y*ml >/dev/null 2>&1 && CI_SYSTEM=github-actions
TEST_RUNNER=""
grep -q '"vitest"' package.json */package.json 2>/dev/null && TEST_RUNNER=vitest
[ -z "$TEST_RUNNER" ] && grep -q '"jest"' package.json */package.json 2>/dev/null && TEST_RUNNER=jest
[ -z "$TEST_RUNNER" ] && { [ -f pyproject.toml ] || ls requirements*.txt >/dev/null 2>&1; } && TEST_RUNNER=pytest
[ -z "$TEST_RUNNER" ] && [ -f go.mod ] && TEST_RUNNER="go test"
[ -z "$TEST_RUNNER" ] && [ -f Cargo.toml ] && TEST_RUNNER="cargo test"
# If fixing CI on a GitHub-Actions repo with gh available: read the most recent failure
if [ "$CI_SYSTEM" = github-actions ] && command -v gh >/dev/null 2>&1; then
gh run list --limit 3
gh run view --log-failed "$(gh run list --limit 1 --json databaseId -q '.[0].databaseId')" 2>/dev/null | tail -80
fi
For non-GitHub CI, read the failing job from that provider (GitLab/CircleCI UI or CLI). For docker logs: parse for ERROR/CRITICAL lines, identify service + file. For Slack thread: extract the bug report and reproduction steps.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 105 lines · 51 tokens per session scan A dfa101ad74a6
fix-bugs is a skill published in the GitHub repository rajitsaha/100xprism (10 stars, last pushed 6d ago), licensed MIT. It adds 51 tokens to every session and 1,029 once invoked, about $0.0003 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 skills, from other repositories
agenttrace-session-audit
Audit local AI coding-agent sessions with agenttrace for cost, tool failures, latency, anomalies, health, diffs, and CI gates.
debugging-expert
Professional Debugging Expert skill. Build performant, secure, and scalable backend logic and RESTful or GraphQL APIs.
flaky-test-fixer
Professional Flaky Test Fixer Expert skill. Implement robust test suites and automated quality checks for modern web/mobile applications.
profiling-guide
Professional Profiling Guide Expert skill. Build performant, secure, and scalable backend logic and RESTful or GraphQL APIs.
api-fuzzing-bug-bounty
Provide comprehensive techniques for testing REST, SOAP, and GraphQL APIs during bug bounty hunting and penetration testing engagements. Covers vulnerability discovery, authentication bypass, IDOR exploitation, and API-specific attack vectors.
api-security-testing
API security testing workflow for REST and GraphQL APIs covering authentication, authorization, rate limiting, input validation, and security best practices.