agentmods.dev

forge

A command for generating a new project skill for a specific technical area. A skill is a reusable set of instructions that guides an agent’s work.

In plain words
What is it for?
Generate starter patterns, behavioral rules, and verification steps for domains such as payment webhooks or OCR processing.
Why use it?
It helps create missing domain guidance before implementation begins and checks whether an existing skill already covers the area.

Command

Part of the project-scaffolder plugin — 7 skills, 19 commands, 2 hooks shipped together

9 1mo ago A scan 33 tokens original MIT
View the source file valsecchi75/project-scaffolder
Install

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.

agentmods
npx agentmods add commands/valsecchi75/project-scaffolder/forge
Clone the repo
git clone --depth 1 https://github.com/valsecchi75/project-scaffolder

Or install project-scaffolder, the plugin that ships this one along with the rest of its 7 skills, 19 commands, 2 hooks.

Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 393 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00033 $0.00393
Opus 5 $0.00016 $0.00197
Sonnet 5 $0.00007 $0.00079
Haiku 4.5 $0.00003 $0.00039

Measured 3d ago against content hash ecc259668b4f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

forge 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 3d 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.

commands/forge.md · 50 lines

What it actually says

/forge

Proactively create a new vertical skill.

Usage

/forge <domain>

Examples

/forge notification-scheduling
/forge ocr-processing
/forge payment-webhook

Steps

  1. Detect the project prefix (from existing skill names, e.g. qs-).
  2. Refuse if a skill already covers this domain — suggest /task --skill <existing> instead.
  3. Read context:
    • wiki/architecture.md
    • wiki/tech-stack.md
    • skills/_synapse-map.md
  4. Analyze the domain name — identify likely patterns, shared libraries, and natural connections.
  5. Generate the new skill at skills/<prefix>-<domain>/SKILL.md:
    • Frontmatter (name, description, maturity: seed, tasks_completed: 0, last_synapse_update: today, connections: [])
    • Overview (from domain + project context)
    • 2-3 starter code patterns from the tech stack
    • Behavioral Rules (Karpathy template)
    • Verification checklist
    • Empty "Common Mistakes" table (Synapse will populate)
  6. Create skills/<prefix>-<domain>/.history/.
  7. Update skills/_synapse-map.md with detected connections and pending_notes: 0.
  8. Ask the user to review before finalizing.

Rules

  • Skill name must follow the project's existing prefix.
  • New skills always start at maturity: seed.
  • Never skip synapse map update.
  • If no connections are detectable: flag the skill as an orphan in the map for future review.
Changes

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.

  1. 3d ago First seen · 50 lines · 33 tokens per session scan A ecc259668b4f

Subscribe to this mod's changes

forge is a command published in the GitHub repository valsecchi75/project-scaffolder (9 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 393 once invoked, about $0.0002 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.

Building agents
Related

Other commands, from other repositories

git

Git operations with intelligent commit messages and workflow optimization.

SuperClaude-Org/SuperClaude_Framework · 11 tokens

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens