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 writingplansgit 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/writingplans)<a href="https://agentmods.dev/skills/carbeneai/forge/writingplans"><img src="https://agentmods.dev/badge/skills/carbeneai/forge/writingplans/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/writingplans"><img src="https://agentmods.dev/badge/skills/carbeneai/forge/writingplans.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.00073 | $0.03753 |
| Opus 5 | $0.00036 | $0.01877 |
| Sonnet 5 | $0.00015 | $0.00751 |
| Haiku 4.5 | $0.00007 | $0.00375 |
Grade A, and why
writing-plans 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 7d 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.
- [ ] User can create account (demo in curl) How it starts
The opening of the file, as written. The whole thing — 646 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Plans
Creates detailed, executable implementation plans that break complex features into granular tasks with exact specifications.
🎯 Load Full CORE Context
read ${PAI_DIR}/skills/CORE/SKILL.md
When to Activate This Skill
- "create implementation plan for X" → Detailed task breakdown
- "plan this feature" → Step-by-step roadmap
- "how should I implement Y" → Design + plan
- "write a plan for Z" → Executable specification
- Before starting complex implementation → Planning phase
Core Philosophy
Granular Task Sizing: 2-5 Minutes Each
Each task should be completable in 2-5 minutes by a skilled developer. This enables:
- Clear progress tracking
- Easy parallelization
- Minimal context switching
- Obvious verification points
Audience: Skilled Developers Unfamiliar with Codebase
Write plans assuming implementer:
- ✅ Knows the programming language and frameworks
- ✅ Understands software development best practices
- ❌ Doesn't know this codebase's structure
- ❌ Hasn't seen the existing code patterns
- ❌ Doesn't know where files are located
Provide exact file paths, show existing patterns, explain integration points.
Methodology: TDD, DRY, YAGNI
- TDD (Test-Driven Development): Write test first, implement to make it pass
- DRY (Don't Repeat Yourself): Reuse existing code, extract common patterns
- YAGNI (You Ain't Gonna Need It): Only implement what's specified, no extras
Plan Structure
Standard Location
docs/plans/YYYY-MM-DD-<feature-name>.md
Example:
docs/plans/2026-02-03-user-authentication.md
docs/plans/2026-02-03-email-notifications.md
Mandatory Headers
Every plan must include:
# [Feature Name] Implementation Plan
**Created:** 2026-02-03
**Status:** Ready for Implementation
**Estimated Time:** [X tasks × 2-5 min = Y-Z minutes total]
## Goal
[1-2 sentences: What are we building and why?]
## Architecture
[High-level approach: What components, how they interact, data flow]
## Tech Stack
[Languages, frameworks, libraries to use. Must match existing codebase.]
## Prerequisites
[What must exist before starting? Dependencies, setup, access required]
## Tasks
[Detailed task list - see below]
## Verification
[How to verify entire implementation is complete]
## Rollback
[How to undo if needed]
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.
- 7d ago First seen · 646 lines · 73 tokens per session scan A 2b000f33fa71
writing-plans is a skill published in the GitHub repository CarbeneAI/Forge (9 stars, last pushed 1mo ago), licensed MIT. It adds 73 tokens to every session and 3,753 once invoked, about $0.0004 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-09-03.
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.