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 commands/rileyhilliard/claude-essentials/setupgit clone --depth 1 https://github.com/rileyhilliard/claude-essentialsWhat 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.00009 | $0.01978 |
| Opus 5 | $0.00005 | $0.00989 |
| Sonnet 5 | $0.00002 | $0.00396 |
| Haiku 4.5 | $0.00001 | $0.00198 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit an existing .claude/ configuration, or bootstrap one for a repository that has none.
Audit-first: Most repos this command runs in already have a .claude/ setup. When the existing configuration is already developed (CLAUDE.md with real content plus rules or settings), bail out early with a short summary of what exists and only the suggestions that are genuinely high-value — report what actually matters, don't pad the list — do NOT regenerate or restructure a working setup. Full generation only happens on repos with no .claude/ or with --force.
Before generating or auditing any files, review the project's existing .claude/ structure and follow Claude Code best practices for writing rules, CLAUDE.md, and skills.
Arguments:
$ARGUMENTS: Optional flags--audit: Only analyze existing config, report improvements--force: Overwrite existing files without confirmation
Mode Detection
- Check if
.claude/directory exists - If exists AND no
--force: Run Audit Mode- If the config is developed (non-trivial CLAUDE.md and rules/ or settings.json), summarize and stop after Step 3's report — apply fixes only if the user asks
- If not exists OR
--force: Run Fresh Init Mode
Note: this command was previously
/ce:init. It was renamed to/ce:setupto avoid colliding with Claude Code's built-in/init.
Configuration Best Practices
All generated files (rules, CLAUDE.md, skills) should follow these principles:
- Rules reference ce:* skills rather than duplicating skill content
- Main files stay concise; split large content into
references/subdirectories - References are always one level deep (no nested references)
Fresh Init Mode
Step 1: Detect Stack
Check for manifest files in the repository root:
| File | Stack | Test Framework |
|---|---|---|
pyproject.toml or requirements.txt |
Python | pytest |
package.json |
Node.js/TypeScript | vitest, jest |
Cargo.toml |
Rust | cargo test |
go.mod |
Go | go test |
pom.xml or build.gradle |
Java/Kotlin | JUnit |
Gemfile |
Ruby | RSpec |
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.
- 3d ago First seen · 239 lines · 9 tokens per session scan A 72d3296286ac
setup is a command published in the GitHub repository rileyhilliard/claude-essentials (128 stars, last pushed 15d ago), licensed MIT. It adds 9 tokens to every session and 1,978 once invoked, about $0.0000 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
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.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.