zerotrustassessment
AGENTS.md435 starsChanged 13 days agoMITView on GitHub
The Zero Trust Assessment PowerShell module runs tenant assessments and generates reports. This file is the entry point for humans and coding agents. Copilot-specific guidance already lives in .github/copilot-instructions.md, and there are repo skills under .github/skills/. For the full suite, build the module and run Pester: A change is done when verify.ps1 and the relevant tests under code-tests/ pass.
We split this AGENTS.md into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 36
Every PR must follow .github/instructions/telemetry.instructions.md.
≈ “Common” is an estimate: at least 1 in 5 of the 36,368 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
AGENTS.md - zerotrustassessment
The Zero Trust Assessment PowerShell module runs tenant assessments and generates
reports. This file is the entry point for humans and coding agents. Copilot-specific guidance
already lives in .github/copilot-instructions.md, and
there are repo skills under .github/skills/.
Repository map
| Path | What lives here |
src/powershell/ | Module source and dependency initialization. |
src/documentgenerator/ | Report and document-generation assets. |
build/ | Build pipeline, configuration, and helpers. |
code-tests/ | Pester commands, structure gates, and assessment tests. |
.github/skills/ | Repository-specific agent skills. |
.github/workflows/, .azure-pipelines/ | CI/CD definitions. |
Conventions
See docs/conventions.md.
Verification / Definition of Done
pwsh scripts/verify.ps1For the full suite, build the module and run Pester:
pwsh build/powershell/Build-PSModule.ps1
Invoke-Pester -Path ./code-testsA change is done when verify.ps1 and the relevant tests under code-tests/ pass.
PR and work-item telemetry
Every PR must follow
.github/instructions/telemetry.instructions.md.
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 28,693 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 repository2 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- psf-support-package-analyzerSkill
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.