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/TechNickAI/ai-coding-configWrote 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/technickai/ai-coding-config/do-issue)<a href="https://agentmods.dev/commands/technickai/ai-coding-config/do-issue"><img src="https://agentmods.dev/badge/commands/technickai/ai-coding-config/do-issue/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/technickai/ai-coding-config/do-issue"><img src="https://agentmods.dev/badge/commands/technickai/ai-coding-config/do-issue.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.00029 | $0.01005 |
| Opus 5.5 | $0.00012 | $0.00402 |
| Sonnet 5.5 | $0.00006 | $0.00201 |
| Haiku 4.5 | $0.00003 | $0.00101 |
Grade A, and why
do-issue 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 25d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/do-issue - Autonomous Issue Resolution
Usage
/do-issue # Auto-detect from branch name
# Patterns: do-issue-123, fix-issue-123, issue-123, fix-123
/do-issue 123 # Explicit issue number
Match patterns in order (extract first capture group):
do-issue-(\d+)fix-issue-(\d+)issue-(\d+)fix-(\d+)
If no match or not on a branch, prompt user for issue number. Validate it's a positive integer before proceeding.
GitHub Interaction
Use gh CLI for all GitHub operations. Use reactions to communicate progress: 👀 when
analyzing, 🚀 when starting work, ❤️ on helpful user comments.
Workflow
Show your decision and rationale briefly. Be professional and thoughtful - these are real users contributing to the project.
For Won't Fix, Need Info, or Invalid: update the issue with explanation and close if appropriate. Done.
For Fix: continue to implementation.
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.
- 25d ago First seen · 131 lines · 29 tokens per session scan A 4087192ffdba
do-issue is a command published in the GitHub repository TechNickAI/ai-coding-config (24 stars, last pushed 26d ago), licensed MIT. It adds 29 tokens to every session and 1,005 once invoked, about $0.0001 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-22.
Other commands, from other repositories
simplify-transform
Apply verified simplifications with user approval. Part of simplify- family.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
reqforge-greenkeeper
Diagnose and fix ReqForge repository release gate failures.
ops-hotfix
Command "ops-hotfix" from christopherlouet/claude-base, covering hotfix agent, request context, objective, workflow and expected output.
fix-issue
A command that takes a GitHub Issue—a tracked bug, request, or question—and guides its fix from investigation through testing and submission. TDD means writing a failing test first, then changing the code until the test passes.
hotfix
An emergency software-fix workflow that moves directly from development to verification and Git commit, skipping the usual planning and design stages.