sage-init
Skill0 starsChanged 5 months agoMITView on GitHub
Bootstrap a new repo for Sage SDLC — creates ./runs/, optional ./Agents.md, .sage-project.json. Use as the first command in a new project before /sage-plan or /sage-orchestrator.
In this repository15 other files it gives its agents.
- Agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/sage-system.mdcCursor rule
- about-sageSkill
- sage-architectSkill
- sage-buildSkill
- sage-designSkill
- sage-devopsSkill
- sage-engineerSkill
- sage-handoffSkill
- sage-orchestratorSkill
- sage-planSkill
- sage-qaSkill
- sage-releaseSkill
- sage-statusSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 2 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
If $HOME/.sage/install.json is missing, stop.
- Distinctive: line 23
Use workspace root as the project directory.
- Very specific: line 24
Create ./runs/ and ./runs/.gitkeep if missing.
- Very specific: line 32
If ./Agents.md is missing, copy $HOME/.sage/Agents.md → ./Agents.md
- Very specific: line 33
If ./Agents.md exists, compare SHA256 to $HOME/.sage/install.json → agents_md_sha256
- Very specific: line 34
If different, refresh from $HOME/.sage/Agents.md (fixes stale copies after global updates)
- Distinctive: line 35
If the user asked to keep local customizations, do not overwrite
- Very specific: line 38
Do not create ./runs/<run-id>/ yet.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
sage-init
You are Sage Init. Prepare the current workspace for Sage runs.
Prerequisites
If $HOME/.sage/install.json is missing, stop. Tell the user to run global install first:
npx agent-sage install --all
# or: cd /path/to/agent-sage && ./scripts/install.sh --allSteps
- Read agents/sage-init.md.
- Use workspace root as the project directory.
- Create
./runs/and./runs/.gitkeepif missing. - Write
./.sage-project.jsonwith:initialized_at(ISO 8601)sage_home:$HOME/.sagesage_versionfrom$HOME/.sage/VERSIONlocal_agents_md: whether./Agents.mdexists in the projectnext_command:sage-orchestrator(default)
- Agents.md — unless the user asked to skip local copy (
--no-agents-md):- If
./Agents.mdis missing, copy$HOME/.sage/Agents.md→./Agents.md - If
./Agents.mdexists, compare SHA256 to$HOME/.sage/install.json→agents_md_sha256 - If different, refresh from
$HOME/.sage/Agents.md(fixes stale copies after global updates) - If the user asked to keep local customizations, do not overwrite
- Record
agents_md_sha256in./.sage-project.json
- If
- CLAUDE.md — if
./CLAUDE.mdis missing and$HOME/.sage/CLAUDE.mdexists, copy it to./CLAUDE.md - Do not create
./runs/<run-id>/yet.
Report
Tell the user:
- What was created or already present
- Whether
./Agents.mdis a fresh copy, pre-existing, or skipped - Whether
./CLAUDE.mdwas copied (if applicable) - Next:
/sage-orchestrator(recommended) or/sage-plan
CLI alternative
npx agent-sage init
# or: /path/to/agent-sage/scripts/install.sh --project .Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

