slashforge-setup

A one-time repository setup command that examines a codebase and creates tailored instructions and development configuration for Claude Code. It can set up both ordinary repositories and monorepos, which contain multiple applications or packages.

In plain words
What is it for?
Use it to create or fill in CLAUDE.md files, rules, skills, agents, commands, and hooks for a repository. It is useful when starting a new project or completing a partial setup.
Why use it?
It removes the need to write repository guidance and agent configuration by hand. It also makes later setup runs safer by detecting which generated files can be refreshed.

Command

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/rajdeepratan/slashforge/slashforge-setup
Clone the repo
git clone --depth 1 https://github.com/rajdeepratan/SlashForge
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 899 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.00023 $0.00899
Opus 5 $0.00012 $0.00449
Sonnet 5 $0.00005 $0.00180
Haiku 4.5 $0.00002 $0.00090

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

Security

Grade A, and why

slashforge-setup 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.

docs/src/content/docs/commands/slashforge-setup.md · 94 lines

How it starts

The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/slashforge:setup

One-time setup for a repository. Explores the codebase, asks clarifying questions, then ==generates a .claude/ configuration tailored to what it found==.

Handles both fresh repos and partial setups — ==if .claude/ already exists, it fills gaps rather than overwriting==.

What it creates

Output Purpose
CLAUDE.md Root instructions — architecture, conventions, intent routing
.claude/rules/ Conventions the agent must follow
.claude/skills/ Repo-specific procedures
.claude/agents/ Specialist agents, plus shared git and code-reviewer
.claude/commands/ Repo-specific commands
.claude/hooks/ Automated behaviours

In a monorepo it creates shared rules and root CLAUDE.md, then app-specific rules, skills, agents, and per-app CLAUDE.md files.

Safe re-runs

Every generated file carries a generated_by marker — YAML frontmatter for .claude/ files, an HTML comment for CLAUDE.md. On re-run the marker decides what happens:

Marker state Behaviour
Present, version current Safe to refresh
Present, version older Stale — proposes a refresh, asks before overwriting
Missing or edited Treated as yours — gaps filled, never overwritten

==Remove or edit the marker on any file you want left alone permanently.==

Monorepos

In a monorepo it creates a root CLAUDE.md with shared rules and global agents, then a separate CLAUDE.md per app with app-specific rules, skills, and specialist agents.

Graphify

During exploration, /slashforge:setup checks language fit for Graphify. If at least 70% of non-trivial source files are in a supported language, it offers to install and index. On YAML, shell, or config-only repos it skips silently.

This is a setup-time offer, not a per-command check. ==It always shows you the exact commands before asking — nothing is installed without your say-so.==

Read the full file on GitHub · 94 lines

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. 2d ago First seen · 94 lines · 23 tokens per session scan A a3c6111fc5df

Subscribe to this mod's changes

slashforge-setup is a command published in the GitHub repository rajdeepratan/SlashForge (5 stars, last pushed 6d ago), licensed MIT. It adds 23 tokens to every session and 899 once invoked, about $0.0001 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.