demo-security-review
Skill1 starsChanged 53 days agoMITView on GitHub
Use when: reviewing demo security, publishing code, integrating demo artifacts, scanning for PII or secrets, or checking authentication and write safety.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- microsoft/frontiertour27-BRK390-building-ai-applications-with-microsoft-databases-and-fabricword for word, first seen Oct 17, 2026
Other versions1 project uses a version of this.
Word for word · 1
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.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- src/caldova-insights/AGENTS.mdAGENTS.md
- caldova-demoSkill
- caldova-campaign-planningSkill
- app-designSkill
- app-validationSkill
- dax-authoringSkill
- fabric-cliSkill
- fabric-sdkSkill
- playwright-cliSkill
- query-designSkill
- rayfin-functionsSkill
- rayfinSkill
- schema-discoverySkill
- visualsSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 11
Run npm run security:publication.
- Very specific: line 16
Run gitleaks git . --redact --exit-code 1 to inspect locally available history.
- Very specific: line 19
Run npm audit and audit the resolved Python environment with pip-audit.
- Distinctive: line 23
Verify negative controls: no token, wrong role, stale case, missing source, dependency failure and uncertain write.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Demo Security Review
Review the actual publication set, including tracked files. Ignore rules do not remove already-tracked content. Do not print secrets or personal values in findings.
- Run
npm run security:publication. It fails on private paths, home paths, personal email patterns, populated notebook outputs and unreviewed binary archives. - Run
node scripts/check-publication.mjs --export, thengitleaks dir build/publication --redact --exit-code 1. Never scan private auth caches to create a public report. Keep detailed findings under ignoredtmp/. - Run
gitleaks git . --redact --exit-code 1to inspect locally available history. History is a separate scope: clean new files do not sanitize old commits. Do not rewrite history, revoke secrets or push without an explicit owner request. - Run
npm auditand audit the resolved Python environment withpip-audit. Fix patchable findings and test compatibility; do not lower the audit threshold. - Review token issuer/audience/expiry/signature, per-operation roles, SQL parameters, idempotency, context binding, least privilege, origin/redirect checks, and errors.
- Verify negative controls: no token, wrong role, stale case, missing source, dependency failure and uncertain write. Tests use injected doubles, never cloud writes.
- Inspect any new image visually and review metadata. Office archives, recordings, screenshots and notebook outputs need separate privacy approval before inclusion.
- Publish a findings-first report with fixes, commands, scope and remaining limits. Pattern scans do not prove that arbitrary free text or pixels contain no PII.
The retained synthetic persona registry is not live user data. Real account IDs, emails, tenant-specific configuration and execution receipts remain private.
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.

