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 CarbeneAI/Forge --skill codingagentgit clone --depth 1 https://github.com/CarbeneAI/ForgeWrote 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/carbeneai/forge/codingagent)<a href="https://agentmods.dev/skills/carbeneai/forge/codingagent"><img src="https://agentmods.dev/badge/skills/carbeneai/forge/codingagent/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/carbeneai/forge/codingagent"><img src="https://agentmods.dev/badge/skills/carbeneai/forge/codingagent.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.00057 | $0.01166 |
| Opus 5.5 | $0.00023 | $0.00466 |
| Sonnet 5.5 | $0.00011 | $0.00233 |
| Haiku 4.5 | $0.00006 | $0.00117 |
Grade A, and why
CodingAgent 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CodingAgent
Orchestrate multiple parallel coding agents using tmux sessions for PTY support and git worktrees for isolated development environments.
Workflow Routing
When executing a workflow, call the notification script via Bash:
${PAI_DIR}/tools/skill-workflow-notification WorkflowName CodingAgent
| Workflow | Trigger | File |
|---|---|---|
| SpawnAgents | "spawn agents", "fix these issues", "parallel coding" | workflows/SpawnAgents.md |
| MonitorSessions | "check agents", "monitor progress", "session status" | workflows/MonitorSessions.md |
| CollectResults | "gather results", "agents done", "merge work" | workflows/CollectResults.md |
Examples
Example 1: Fix multiple GitHub issues in parallel
User: "Fix issues #123, #124, and #125 in parallel"
→ Invokes SpawnAgents workflow
→ Creates git worktrees for each issue
→ Spawns tmux sessions with Claude Code agents
→ Each agent works on one issue independently
→ Notifies via Telegram when complete
Example 2: Check progress on parallel agents
User: "How are my coding agents doing?"
→ Invokes MonitorSessions workflow
→ Lists active pai-agent-* tmux sessions
→ Captures recent output from each
→ Reports status and progress
Example 3: Collect finished work
User: "Gather the results from all agents"
→ Invokes CollectResults workflow
→ Checks which agents have completed
→ Summarizes changes per worktree
→ Provides merge instructions
Key Concepts
Why tmux?
Claude Code requires a pseudo-terminal (PTY) for interactive features. tmux provides:
- PTY allocation - Full terminal emulation for Claude Code
- Session persistence - Agents continue running if connection drops
- Output capture - Retrieve agent output without interrupting
- Parallel execution - Multiple independent sessions
Socket Isolation
All PAI agent sessions use a dedicated socket:
SOCKET="${TMPDIR:-/tmp}/pai-agents.sock"
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- TmuxPatterns.md 4.6 KB
- tools/AgentLauncher.ts 6.8 KB runs code
- tools/Manage.sh 2.6 KB runs code
- tools/SessionManager.ts 6.9 KB runs code
- tools/WorktreeManager.ts 7.2 KB runs code
- workflows/CollectResults.md 2.9 KB
- workflows/MonitorSessions.md 2.0 KB
- workflows/SpawnAgents.md 2.7 KB
- WorktreeGuide.md 5.1 KB
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 · 166 lines · 57 tokens per session scan A c6190b5ab229
CodingAgent is a skill published in the GitHub repository CarbeneAI/Forge (9 stars, last pushed 2mo ago), licensed MIT. It adds 57 tokens to every session and 1,166 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-08-31.
Other skills, from other repositories
scanning-containers-with-trivy-in-cicd
This skill covers integrating Aqua Security's Trivy scanner into CI/CD pipelines for comprehensive container image vulnerability detection. It addresses scanning Docker images for OS package and application dependency CVEs, detecting misconfigurations in Dockerfiles, scanning filesystem and git repositories, and…
implementing-code-signing-for-artifacts
This skill covers implementing code signing for build artifacts to ensure integrity and authenticity throughout the software supply chain. It addresses signing binaries, packages, and containers using GPG, Sigstore, and platform-specific signing tools, establishing trust chains, and verifying signatures in deployment…
implementing-semgrep-for-custom-sast-rules
Write custom Semgrep SAST rules in YAML to detect application-specific vulnerabilities, enforce coding standards, and integrate into CI/CD pipelines.
building-vulnerability-dashboard-with-defectdojo
Deploy DefectDojo as a centralized vulnerability management dashboard with scanner integrations, deduplication, metrics tracking, and Jira ticketing workflows.
panguard
AI agent security platform — audit skills, scan for threats, and run 24/7 protection with 9,700+ detection rules.
detecting-aws-credential-exposure-with-trufflehog
Detecting exposed AWS credentials in source code repositories, CI/CD pipelines, and configuration files using TruffleHog, git-secrets, and AWS-native detection mechanisms to prevent credential theft and unauthorized account access.