agent-sage
CLAUDE.md0 starsChanged 5 months agoMITView on GitHub
This repo is the Sage SDLC agent system. The root contract is Agents.md, not this file. Read Agents.md first, before doing any work here, even if no /sage-* command was typed. It defines the agent registry, workflow profiles, stack preferences, and global rules that apply to every phase agent in agents/. If the task is plan/design/architect/build/qa/devops/release work, use the matching /sage-* skill in .cursor/skills/ rather than improvising. See README.md for the full command list.
In this repository15 other files it gives its agents.
- Agents.mdAGENTS.md
- .cursor/rules/sage-system.mdcCursor rule
- about-sageSkill
- sage-architectSkill
- sage-buildSkill
- sage-designSkill
- sage-devopsSkill
- sage-engineerSkill
- sage-handoffSkill
- sage-initSkill
- sage-orchestratorSkill
- sage-planSkill
- sage-qaSkill
- sage-releaseSkill
- sage-statusSkill
The file
We split this CLAUDE.md into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 5
Read Agents.md first, before doing any work here, even if no /sage-* command was typed.
- Very specific: line 7
If the task is plan/design/architect/build/qa/devops/release work, use the matching /sage-* skill in .cursor/skills/ rather than …
≈ “Common” is an estimate: at least 1 in 5 of the 27,641 CLAUDE.md 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
This repo is the Sage SDLC agent system. The root contract is Agents.md, not this file.
Read Agents.md first, before doing any work here, even if no /sage-* command was typed. It defines the agent registry, workflow profiles, stack preferences, and global rules that apply to every phase agent in agents/.
If the task is plan/design/architect/build/qa/devops/release work, use the matching /sage-* skill in .cursor/skills/ rather than improvising. See README.md for the full command list.
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.

