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 skills add geronimo-iia/agent-skills --skill coding-agentgit clone --depth 1 https://github.com/geronimo-iia/agent-skillsWrote 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/geronimo-iia/agent-skills/coding-agent)<a href="https://agentmods.dev/skills/geronimo-iia/agent-skills/coding-agent"><img src="https://agentmods.dev/badge/skills/geronimo-iia/agent-skills/coding-agent/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/skills/geronimo-iia/agent-skills/coding-agent"><img src="https://agentmods.dev/badge/skills/geronimo-iia/agent-skills/coding-agent.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.00055 | $0.01114 |
| Opus 5.5 | $0.00022 | $0.00446 |
| Sonnet 5.5 | $0.00011 | $0.00223 |
| Haiku 4.5 | $0.00006 | $0.00111 |
Grade A, and why
coding-agent 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.
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coding Agent (background-first)
Use bash background mode for non-interactive coding work. For interactive sessions, use tmux.
Core pattern: workdir + background
# Create isolated workspace
SCRATCH=$(mktemp -d)
# Launch agent in scoped directory
bash workdir:$SCRATCH background:true command:"claude \"Your task\""
# Returns sessionId
# Monitor
process action:log sessionId:XXX
process action:poll sessionId:XXX
# Send input if agent asks a question
process action:write sessionId:XXX data:"y"
# Kill if needed
process action:kill sessionId:XXX
Why workdir matters: agent starts in a focused directory and doesn't
read unrelated files. Scope the working directory to only what the task needs.
Claude Code
bash workdir:~/project background:true command:"claude \"Your task\""
Non-interactive flag (--print / -p) for one-shot output:
bash workdir:~/project background:true command:"claude -p \"Summarize src/\""
Parallel PR reviews with git worktrees
For reviewing multiple PRs in parallel without branch conflicts:
# Fetch all PR refs
git fetch origin '+refs/pull/*/head:refs/remotes/origin/pr/*'
# One agent per PR — no checkout conflicts
bash workdir:~/project background:true command:"claude \"Review PR #86. git diff origin/main...origin/pr/86\""
bash workdir:~/project background:true command:"claude \"Review PR #87. git diff origin/main...origin/pr/87\""
# Monitor all
process action:list
# Post results
process action:log sessionId:XXX
gh pr comment <PR#> --body "<review content>"
Never checkout branches for parallel reviews — git diff the refs directly
so agents don't conflict.
Parallel issue fixing with git worktrees + tmux
For fixing multiple issues in parallel with full isolation:
# 1. Clone to temp location
cd /tmp && git clone [email protected]:user/repo.git repo-worktrees
cd repo-worktrees
# 2. One worktree per issue
git worktree add -b fix/issue-78 /tmp/issue-78 main
git worktree add -b fix/issue-99 /tmp/issue-99 main
# 3. tmux sessions
SOCKET="${TMPDIR:-/tmp}/fixes.sock"
tmux -S "$SOCKET" new-session -d -s fix-78
tmux -S "$SOCKET" new-session -d -s fix-99
# 4. Launch agent in each
tmux -S "$SOCKET" send-keys -t fix-78 "cd /tmp/issue-78 && claude 'Fix issue #78: <description>. Commit and push.'" Enter
tmux -S "$SOCKET" send-keys -t fix-99 "cd /tmp/issue-99 && claude 'Fix issue #99: <description>. Commit and push.'" Enter
# 5. Monitor
tmux -S "$SOCKET" capture-pane -p -t fix-78 -S -30
# 6. Check done (prompt returned)
tmux -S "$SOCKET" capture-pane -p -t fix-78 -S -3 | grep -q "❯" && echo "Done!"
# 7. Create PRs
cd /tmp/issue-78 && git push -u origin fix/issue-78
gh pr create --repo user/repo --head fix/issue-78 --title "fix: ..." --body "..."
# 8. Cleanup
tmux -S "$SOCKET" kill-server
git worktree remove /tmp/issue-78
git worktree remove /tmp/issue-99
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 · 129 lines · 55 tokens per session scan A 5695b09a4872
coding-agent is a skill published in the GitHub repository geronimo-iia/agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 1,114 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-05.
Other skills, from other repositories
commit
Skill "commit" from clacky-ai/openclacky, covering smart commit skill, critical requirement: single-line commits only, core philosophy, usage and process steps.
re0-git
Rewrite a finished commit's message into a clean, handoff-ready form in your own log style, so git log alone tells the story. User-invoked: run it after a commit.
devops-pipeline
Configure pre-commit hooks and lean GitHub Actions for shift-left quality assurance. Use when adding or auditing CI/CD to maximize local test coverage and minimize CI cost. Skip for Terraform/K8s, deployment pipelines, or non-GitHub CI providers.
auto-push
Generate a commit message, stage all changes, and push to remote after scanning for secrets, large files, and protected-branch risks. Skip for opening PRs, code review, or cutting releases/tags.
azure-repos
Expert knowledge for Azure Repos development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, and integrations & coding patterns. Use when managing Git/TFVC repos, branch policies/PR checks, TFVC→Git migrations, large files, or…
hashiiiii-git
Use this skill to name a Git branch or write a commit message.