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/dimitrigeelen/agentic-engineering-framework/new-projectgit clone --depth 1 https://github.com/DimitriGeelen/agentic-engineering-frameworkWrote 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/commands/dimitrigeelen/agentic-engineering-framework/new-project)<a href="https://agentmods.dev/commands/dimitrigeelen/agentic-engineering-framework/new-project"><img src="https://agentmods.dev/badge/commands/dimitrigeelen/agentic-engineering-framework/new-project.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00574 |
| Opus 5 | $0.00000 | $0.00287 |
| Sonnet 5 | $0.00000 | $0.00115 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
new-project 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 today.
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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/new-project - Initialize New Project
Guided onboarding for setting up a new project with the Agentic Engineering Framework.
Step 1: Gather Info
Ask the user (using AskUserQuestion with two questions):
- Project path — "What is the path to your project directory?"
- Options: "Current directory", "Enter path"
- AI provider — "Which AI provider will you use?"
- Options: "Claude (Recommended)", "Cursor", "Generic (any provider)"
Map provider answers: "Claude" → claude, "Cursor" → cursor, "Generic" → generic.
Step 2: Verify Prerequisites
Run in parallel:
fw doctor— check framework healthls {project_path}— verify path exists (create withmkdir -pif not)- Check if path already has
.framework.yaml— warn if re-initializing
If fw doctor shows failures, stop and help fix them first.
Step 3: Initialize Git (if needed)
Check if the project directory has a git repo:
git -C {project_path} rev-parse --git-dir 2>/dev/null
If not, initialize:
git init {project_path}
Step 4: Run fw init
fw init {project_path} --provider {provider}
Report what was created. If init fails, diagnose and fix.
Step 5: Verify Setup
cd {project_path}
fw doctor
Report results. All checks should pass. Fix any failures before proceeding.
Step 6: Start First Session
cd {project_path}
fw context init
Step 7: Create First Task
Ask the user: "What's the first thing you want to work on?"
Then run:
cd {project_path}
fw work-on "{user_description}" --type build
Print confirmation:
Project initialized and ready!
- Path: {project_path}
- Provider: {provider}
- First task: T-XXX ({task_name})
You're all set. Start coding!
Rules
- This skill is for NEW projects only. For existing projects, use
fw work-on. - Always create a git repo before running
fw init(it requires git hooks). - If the directory doesn't exist, create it with
mkdir -p. - If re-initializing an existing project, warn the user and require confirmation.
- Run
fw doctorboth before (framework check) and after (project check) init. - The skill ends by creating the first task — the user should be ready to work immediately.
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.
- today First seen · 89 lines · 0 tokens per session scan A 1f97379fad6e
new-project is a command published in the GitHub repository DimitriGeelen/agentic-engineering-framework (13 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 574 tokens. 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-09-04.
Other commands, from other repositories
service-check
Request each agent to run a self-diagnostic to validate their runtime setup.
compatibility-audit
Audit all agents for Trinity compatibility by requesting self-diagnostics from each agent.
request-research
Ask the researcher to investigate a specific topic.
health
Perform a health check on all agents and identify any issues.
schedules
Quick overview of all schedules across the platform.
status
Report on recent research activity and findings count.