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/mark22013333/crewWrote 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/mark22013333/crew/bug-intake-refiner)<a href="https://agentmods.dev/agents/mark22013333/crew/bug-intake-refiner"><img src="https://agentmods.dev/badge/agents/mark22013333/crew/bug-intake-refiner/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/mark22013333/crew/bug-intake-refiner"><img src="https://agentmods.dev/badge/agents/mark22013333/crew/bug-intake-refiner.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.00073 | $0.00528 |
| Opus 5.5 | $0.00029 | $0.00211 |
| Sonnet 5.5 | $0.00015 | $0.00106 |
| Haiku 4.5 | $0.00007 | $0.00053 |
Grade A, and why
bug-intake-refiner 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 17d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 17d ago First seen · 67 lines · 73 tokens per session scan A 3a13d2317503
bug-intake-refiner is an agent published in the GitHub repository mark22013333/crew (9 stars, last pushed 5d ago), with no licence file. It adds 73 tokens to every session and 528 once invoked, about $0.0003 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-10-02.
Other agents, from other repositories
incident-responder
Production incident response agent'i. Severity classification (P0-P3), runbook execution, root cause analysis, impact assessment, communication template'leri, post-incident review ve remediation tracking.
Compliance Auditor
Perform non-destructive cross-artifact consistency and quality analysis across spec, plan, and tasks.
linear-ticket-investigator
Extract evidence from a single Linear ticket — read the ticket, locate affected code, and return an Evidence Record matching the /fix-bug Phase 2 schema. Returns structured evidence only — no root-cause analysis, no fix proposal, no confidence scoring (those are /fix-bug's job via holistic-analysis). Used by…
evolve-scout-scan
MAP-step slice scanner for the scout map-reduce decomposition. Scans ONE codebase slice (a package group) and emits a structured ScanDigest. Does NOT select tasks or write evals — the scout synthesizer (REDUCE) does that from the merged digests.
project-rules-drift-auditor
Detects drift between live GitHub Project automation rules and the canonical AIDL guardrail baseline. USE FOR: scheduled drift audits of project automation rules, comparing live rule configuration against a baseline manifest, classifying drift severity, generating issue-ready remediation output, and running advisory…
incident-to-backlog-router
Automates routing of incident signals into prioritized backlog or maintenance work items with required portfolio fields pre-populated and closure linkage tracked. USE FOR: create GitHub issues from incident metadata with Type/Priority/Risk/Guardrail State/SRE Impact pre-filled, route incidents to sprint or maintenance…