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/forgeailab/forge/forge-project-agentnpx skills add ForgeAILab/forge --skill forge-project-agentgit clone --depth 1 https://github.com/ForgeAILab/forgeWhat 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.00106 | $0.01052 |
| Opus 5 | $0.00053 | $0.00526 |
| Sonnet 5 | $0.00021 | $0.00210 |
| Haiku 4.5 | $0.00011 | $0.00105 |
Grade A, and why
forge-project-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 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forge Project Agent
Operate as the persistent planner and orchestrator for one authenticated Project. Load operating-contract.md completely before bootstrap or any Project-scoped mutation.
The runtime contract is forge.project.orchestration/v1. Derive Project ID, binding, policy, and permission ceiling from the authenticated runtime—never from model arguments or handoff prose.
Workflow
- Verify binding and the project-visible handoff against the exact approved Charter ID/revision/content digest/render digest/receipt and selected identity/Profile/skill revisions. Fail closed on any mismatch.
- Load domain-specific Effective Project State: approved Charter for identity/scope, active baseline and Documents for execution intent, active Decisions, authoritative Task events, principal-bound validation, milestones, readiness, releases, commitments, and context provenance.
- Acknowledge inherited outcome, fixed boundaries, mode, open assumptions/research, baseline/milestone state, and the next setup action. Do not re-interview settled Charter decisions.
- Choose the smallest safe artifact set. Use one Delivery Brief for compact low-risk work; use only applicable Research, Product, Design, Architecture, and Execution Plan artifacts for standard work.
- Propose one digest-bound execution baseline with plan items, acceptance/evidence matrix, release policy, capability/risk classes, adaptive envelope, elevated operations, and rollback/recovery. Only the user activates it.
- Before activation, allow only non-mutating discovery/planning Tasks and non-runnable implementation plans. After activation, manage traceable Tasks through
TaskService; Workers/reviewers alone receive scheduler-issued Workspace leases. - Reconcile Task outcomes into Documents, Decisions, commitments, and milestones. Keep live progress separate from validated truth.
- Ask Forge for standalone readiness. The Project Agent may propose; Forge computes; only the user may attest, waive, or release. Release names the exact readiness snapshot/digest and creates an immutable
Mxxx-rNmanifest.
What ships with it
2 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.
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 · 61 lines · 106 tokens per session scan A 2ad9d35593f0
forge-project-agent is a skill published in the GitHub repository ForgeAILab/forge (54 stars, last pushed 16d ago), licensed MIT. It adds 106 tokens to every session and 1,052 once invoked, about $0.0005 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-30.
Other skills, from other repositories
treework-manual
Use TreeWork Manual when the user asks for it, or when the Agent judges that organizing ongoing, multi-part work as a persistent Markdown Tree would improve direction, continuity, recovery, or handoff. Adapt the Tree's depth and document detail to the user's needs, domain, and situation rather than a fixed threshold.
treework
Use TreeWork, a tree-guided development plugin for complex or evolving software projects that need staged alignment, pre-coding technical Specs, declarative project-tree planning, branch-scoped Git worktrees, durable recovery, and protected completion. It teaches the Agent to move through development along the Tree…
ramble
Run a human-feedback loop through RambleDesk. Hard trigger: when the user invokes /ramble, $ramble, [$ramble], or says to use RambleDesk/ramble feedback, create a RambleDesk request before answering the substance unless they explicitly say not to send one. Also use when real human judgment, review, approval, or…
documentation-sync
Use for any code change, specification change, architecture change, or agent-rule change; do not use as a replacement for the canonical spec.
implement-change
Use for every code change in RepoGrammar; do not use for documentation-only edits that do not touch behavior or repository automation.
major-feature-workflow
Use when a change adds user-visible capability, changes public API, MCP contract, storage schema, module boundaries, indexing pipeline, or important dependencies.