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 agentmods add skills/mr-tbot/auto-everything/auto-issue-fixnpx skills add mr-tbot/Auto-Everything --skill auto-issue-fixgit clone --depth 1 https://github.com/mr-tbot/Auto-EverythingWrote 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/mr-tbot/auto-everything/auto-issue-fix)<a href="https://agentmods.dev/skills/mr-tbot/auto-everything/auto-issue-fix"><img src="https://agentmods.dev/badge/skills/mr-tbot/auto-everything/auto-issue-fix.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 | $0.00105 | $0.03661 |
| Opus 5 | $0.00053 | $0.01831 |
| Sonnet 5 | $0.00021 | $0.00732 |
| Haiku 4.5 | $0.00011 | $0.00366 |
Grade A, and why
auto-issue-fix scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**Forgejo/Gitea.** `gh` does not target it. Use `tea`, or curl `/api/v1` with `Authorization: token …`, How it starts
The opening of the file, as written. The whole thing — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/auto-issue-fix
Find what users reported, fix what is real, prove the fix, and reply — across every tracker the repo can reach.
The governing rule: reading is cheap, writing is public and permanent. A comment fires notifications to everyone watching, a close tells a reporter their problem is over, and a store-review reply publishes under your app's name to every prospective installer. This skill reads freely and writes under gates.
Step 1 — Discover The Sources
Detect from inside the repo rather than asking cold: URLs in README/CONTRIBUTING/issue templates,
ticket-ID patterns (PROJ-123) in commits and branch names, CI integrations, .env keys, .mcp.json,
crash-reporter SDK config (sentry.properties, google-services.json, firebase.json).
Then confirm the list with the user, including which ones you may write to.
Crash reporters are the highest-signal source and the most commonly misdescribed:
- Firebase Crashlytics has no public REST API for reading crashes. The documented programmatic path is the BigQuery export. Any plan that says "query the Crashlytics API for the stack trace" is wrong.
- Google Play: the read path for crashes/ANRs is the Play Developer Reporting API
(
playdeveloperreporting.googleapis.com) — read-only, and a different API fromandroidpublisher.androidpublisher reviews.listreturns roughly the last 7 days only; older reviews need the Console CSV export. - Sentry has a full API, covered below.
- App Store Connect auth is a short-lived ES256 JWT, 20-minute maximum lifetime.
Symbolication is a prerequisite, not a footnote. An obfuscated trace is unusable. Before trying to
read stack traces, confirm the mapping exists for the crashing build: R8/ProGuard mapping.txt and
native symbols uploaded per versionCode, dSYMs or source maps uploaded to Sentry. No mapping, no
diagnosis — say so instead of guessing at frames.
Step 2 — Classify Before Touching Anything
Seven outcomes. Guessing here is what produces bad automated comments:
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.
- 4d ago First seen · 254 lines · 105 tokens per session scan A 32980a12619e
auto-issue-fix is a skill published in the GitHub repository mr-tbot/Auto-Everything (7 stars, last pushed 2d ago), licensed MIT. It adds 105 tokens to every session and 3,661 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
subagent-delegation
Canonical protocol for delegating GSD work to native Antigravity subagents — when to delegate, how to invoke, workspace isolation modes, and the inline fallback for older IDE versions.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
project-init
Scaffold an unconfigured directory into a configured pi project. Interactive, profile-driven: previews the planned writes, then writes AGENTS.md, .pi/settings.json and prompt files — optionally also a knowledge base, an openspec/ scaffold, and user-global /.pi/agent/settings.json. Use on a bare directory, or when the…