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/s3yed/appie-kit/coding-agentsnpx skills add S3YED/appie-kit --skill coding-agentsgit clone --depth 1 https://github.com/S3YED/appie-kitWhat 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.00055 | $0.03148 |
| Opus 5 | $0.00028 | $0.01574 |
| Sonnet 5 | $0.00011 | $0.00630 |
| Haiku 4.5 | $0.00006 | $0.00315 |
Grade A, and why
coding-agents 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 2d 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 — 319 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coding Agents — Delegate to AI Coding CLIs
Delegate coding to external autonomous AI coding agent CLIs via Hermes terminal/process tools. This umbrella covers Claude Code (Anthropic), Codex (OpenAI), and OpenCode (provider-agnostic, open-source), plus the Kanban Codex Lane pattern for Hermes Kanban workers.
When to Use Coding Agents
Use any coding agent CLI when:
- Building features, refactoring, or batch fixing issues
- The task requires autonomous file exploration and multi-step reasoning
- You want to run parallel implementation lanes
Do NOT use a coding agent when:
- A small direct edit is faster and safer
- The change touches secrets, credentials, or production order-entry systems
- You need human judgment that can't be captured in a prompt
Shared Prerequisites
All coding agents need:
- A git repository — most refuse to run outside one
- Auth credentials (agent-specific, see sections below)
pty=truefor interactive TUI sessions; print/one-shot mode may not need it
Section 1: Claude Code
Anthropic's autonomous coding agent CLI. v2.x can read files, write code, run shell commands, spawn subagents, and manage git workflows.
Install & Auth
npm install -g @anthropic-ai/claude-code
claude auth login # Browser OAuth
claude auth login --console # API key billing
claude auth login --sso # Enterprise SSO
claude auth status # Verify
Print Mode (PREFERRED for one-shot tasks)
# Non-interactive, exits when done. No PTY needed.
terminal(command="claude -p 'Add error handling to all API calls in src/' --allowedTools 'Read,Edit' --max-turns 10", workdir="/path/to/project", timeout=120)
Key flags: --allowedTools 'Read,Edit', --max-turns N, --max-budget-usd N, --output-format json, --json-schema '{...}', --continue (resume last session), --resume <id> (specific session), --bare (fastest startup, needs ANTHROPIC_API_KEY).
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.
- 2d ago First seen · 319 lines · 55 tokens per session scan A 86290b1e5e32
coding-agents is a skill published in the GitHub repository S3YED/appie-kit (6 stars, last pushed 6d ago), licensed MIT. It adds 55 tokens to every session and 3,148 once invoked, about $0.0003 per session on Opus 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-08-31.
Other skills, from other repositories
task-intelligence
Activate for: brain dump, prioritise, P1 P2 P3, critical path, daily priorities, weekly planning, backlog review, cross-domain plan, what should I work on, capture everything in my head, sort my priorities, what is most important right now, weekly critical path. NOT for: basic task CRUD (use official productivity…
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
setup-matt-pocock-skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
accessibility
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.