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.
git clone --depth 1 https://github.com/sruja-ai/srujaWrote 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/commands/sruja-ai/sruja/sruja-bugfix-triage)<a href="https://agentmods.dev/commands/sruja-ai/sruja/sruja-bugfix-triage"><img src="https://agentmods.dev/badge/commands/sruja-ai/sruja/sruja-bugfix-triage/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/commands/sruja-ai/sruja/sruja-bugfix-triage"><img src="https://agentmods.dev/badge/commands/sruja-ai/sruja/sruja-bugfix-triage.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.00000 | $0.00522 |
| Opus 5 | $0.00000 | $0.00261 |
| Sonnet 5 | $0.00000 | $0.00104 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
sruja-bugfix-triage 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 10d 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.
What it actually says
Sruja: Bugfix Triage
Systematic workflow for triaging and fixing bugs with architecture grounding.
Related: plan-feature → implement-from-plan → verify-task → reflect-on-run
Steps
-
Reproduce the bug
- Understand the failure mode
- Identify the affected file(s) and component(s)
-
Get focus briefing
sruja focus --file <buggy-file> -r . -f for-aiThis gives you the blast radius, decisions, and AI instructions for the target.
-
Search memory for similar issues
sruja agent history -r . -f json # Or MCP: sruja_search_memory with the error messageCheck if this bug (or similar) has been encountered before.
-
Form a hypothesis
- What component is broken?
- What change would fix it?
- What's the blast radius of the fix?
-
Create a minimal fix plan
- Scope the change to the smallest possible diff
- Identify which verification steps will validate the fix
-
Implement the fix
- Make the minimal change
- Do not refactor unrelated code
-
Verify with bugfix profile
sruja verify-task --profile bugfix --file <buggy-file> -r . -
If verify fails:
- Review the failed step
- Fix and re-verify
- Record a correction learning
-
If verify passes:
- Optionally record an affirmation learning
- Mark the bug as fixed
Example
# Bug: auth token validation fails on edge cases
sruja focus --file src/auth/token.rs -r . -f for-ai
sruja agent history -r . -f json # Check for similar auth bugs
# ... implement fix ...
sruja verify-task --profile bugfix --file src/auth/token.rs -r .
References
- docs/HOST_AGENT_INTEGRATION.md — Run envelope
- AGENTS.md — Build and test commands
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.
- 10d ago First seen · 67 lines · 0 tokens per session scan A 7126e9276351
sruja-bugfix-triage is a command published in the GitHub repository sruja-ai/sruja (24 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 522 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-30.
Other commands, from other repositories
review-drift
Walk the VibeFrame drift inbox and resolve each finding (fix / accept / dismiss).
debug
Systematic debugging: reproduce, isolate, hypothesize, fix, verify, document.
api-aqa-flow-execution-and-report-analysis
Phase 6 Execution & Report Analysis of api-aqa-flow (USER INTERACTION REQUIRED).
fire-resurrect
Autonomous Resurrection Mode — reverse-engineer intent from messy code, then rebuild clean from scratch.
fire-reflect
After any failure (debug resolution, test failure, approach rotation, stalled loop), capture what was tried, why it failed, and what actually worked as a persistent reflection. Future sessions search these before investigating.
fire-verify-uat
Conversational User Acceptance Testing with automatic parallel diagnosis on failures.