frontier-ai-starter-kit-rvas
AGENTS.md7 starsChanged 20 days agoMITView on GitHub
Before drafting, editing, or returning repository prose, invoke humanize-content. This includes documentation, Markdown, and user-facing explanations. Do not apply it to files under plugins/ or to AGENTS.md. Use TONE-OF-VOICE.md unless the user requests another voice. Write for competent engineers: lead with the point, use concrete verbs, name the actor when it matters, and explain complexity only when the reader needs it. Preserve technical facts, Microsoft product names, dates, citations, and governance terms. Apply diminishing returns: keep material only when it…
1 other project uses a version of this.
Adopted by
Most recently taken up by
- microsoft/frontier-agentic-cobuild-rvasword for word, first seen Oct 24, 2026
Other versions1 project uses a version of this.
Word for word · 1
- microsoft/frontier-agentic-cobuild-rvas★ 7100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,700 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository28 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- azure-aigatewaySkill
- azure-aiSkill
- diagram-designSkill
- excalidraw-diagramSkill
- humanize-contentSkill
- impeccableSkill
- finetuningSkill
- capacitySkill
- customizeSkill
- presetSkill
- deploy-modelSkill
- microsoft-foundrySkill
- rvap-brandSkill
- writing-for-agentsSkill
- agentic-workflowsSkill
- content-accuracy-auditSkill
- foundry-hosted-agentsSkill
- foundry-iq-knowledge-basesSkill
- foundry-modelsSkill
- foundry-observabilitySkill
- foundry-projects-resourcesSkill
- foundry-toolboxesSkill
- foundry-workflowsSkill
- impeccableSkill
- ai-agent-creatorSkill
- cloud-architecture-diagramSkill
- idea-forgeSkill
The file
We split this AGENTS.md into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 5
Before drafting, editing, or returning repository prose, invoke humanize-content.
- Distinctive: line 9
Use TONE-OF-VOICE.md unless the user requests another voice.
- Distinctive: line 10
Write for competent engineers: lead with the point, use concrete verbs, name the actor when it matters, and explain complexity only when …
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.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
Repository instructions
Writing
Before drafting, editing, or returning repository prose, invoke
humanize-content. This includes documentation, Markdown, and user-facing
explanations. Do not apply it to files under plugins/ or to AGENTS.md.
Use TONE-OF-VOICE.md unless the user requests another voice. Write for competent engineers: lead with the point, use concrete verbs, name the actor when it matters, and explain complexity only when the reader needs it. Preserve technical facts, Microsoft product names, dates, citations, and governance terms.
Relevance and source of truth
Apply diminishing returns: keep material only when it changes the reader's understanding, decision, or next action. Remove repetition, generic benefits, and steps or deliverables that do not help the reader act.
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.