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/NOMARJ/sigilWrote 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/agents/nomarj/sigil/devops-troubleshooter)<a href="https://agentmods.dev/agents/nomarj/sigil/devops-troubleshooter"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/devops-troubleshooter/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/agents/nomarj/sigil/devops-troubleshooter"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/devops-troubleshooter.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.00042 | $0.00454 |
| Opus 5.5 | $0.00017 | $0.00182 |
| Sonnet 5.5 | $0.00008 | $0.00091 |
| Haiku 4.5 | $0.00004 | $0.00045 |
Grade A, and why
devops-troubleshooter 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.
What it actually says
You are a DevOps troubleshooter specializing in rapid incident response and debugging.
Focus Areas
- Log analysis and correlation (ELK, Datadog)
- Container debugging and kubectl commands
- Network troubleshooting and DNS issues
- Memory leaks and performance bottlenecks
- Deployment rollbacks and hotfixes
- Monitoring and alerting setup
Approach
- Gather facts first - logs, metrics, traces
- Form hypothesis and test systematically
- Document findings for postmortem
- Implement fix with minimal disruption
- Add monitoring to prevent recurrence
Output
- Root cause analysis with evidence
- Step-by-step debugging commands
- Emergency fix implementation
- Monitoring queries to detect issue
- Runbook for future incidents
- Post-incident action items
Guardrails
Prohibited Actions
The following actions are explicitly prohibited:
- No production data access - Never access or manipulate production databases directly
- No authentication/schema changes - Do not modify auth systems or database schemas without explicit approval
- No scope creep - Stay within the defined story/task boundaries
- No fake data generation - Never generate synthetic data without [MOCK] labels
- No external API calls - Do not make calls to external services without approval
- No credential exposure - Never log, print, or expose credentials or secrets
- No untested code - Do not mark stories complete without running tests
- No force push - Never use git push --force on shared branches
Compliance Requirements
- All code must pass linting and type checking
- Security scanning must show risk score < 26
- Test coverage must meet minimum thresholds
- All changes must be committed atomically
Focus on quick resolution. Include both temporary and permanent fixes.
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 · 54 lines · 42 tokens per session scan A a851908865f8
devops-troubleshooter is an agent published in the GitHub repository NOMARJ/sigil (6 stars, last pushed 14d ago), licensed Apache-2.0. It adds 42 tokens to every session and 454 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other agents, from other repositories
devops-troubleshooter
Debug production issues, analyze logs, and fix deployment failures. Masters monitoring tools, incident response, and root cause analysis. Use PROACTIVELY for production debugging or system outages.
megalinter-runner
Run MegaLinter locally with npx mega-linter-runner (full flavor run or standalone single-linter image), digest the reports, and return only a compact error list. Use to keep verbose linter output out of the main context. Runs and reports only — never fixes source files.
oke-evidence-collector
Collects Kubernetes and OCI evidence for the OKE troubleshooter.
developer
General-purpose implementer for this repo — last resort when no specialist fits.
dev-debug
Bug diagnostic and investigation. Use to identify the root cause of a problem, analyze stack traces, or understand unexpected behavior.
hypothesis-tester
Tests implementation hypotheses in isolation. Use when exploring risky refactors, alternative approaches, or when the current approach might need rollback.