team-security
Skill0 starsChanged 4 months agoMITView on GitHub
Use when auditing save data integrity, checking for cheat vectors, reviewing data validation, or hardening the game against exploits. Routes to the correct workflow pattern and executes step-by-step.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- Shehabov/ai-dev-crewtheir own version, first seen Sep 30, 2026
- gonimar/claude-web-studiotheir own version, first seen Sep 27, 2026
- andeya/team-skillstheir own version, first seen Jun 27, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- andeya/team-skills★ 4same name
- gonimar/claude-web-studio★ 4same name
- Shehabov/ai-dev-crew★ 4same name
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 repository68 other files it gives its agents.
- adoptSkill
- architecture-decisionSkill
- architecture-reviewSkill
- art-bibleSkill
- asset-specSkill
- brainstormingSkill
- bug-reportSkill
- bug-triageSkill
- code-reviewSkill
- consistency-checkSkill
- content-auditSkill
- create-architectureSkill
- create-control-manifestSkill
- create-epicsSkill
- create-storiesSkill
- day-one-patchSkill
- design-reviewSkill
- design-systemSkill
- dev-storySkill
- dispatching-parallel-agentsSkill
- estimateSkill
- executing-plansSkill
- finishing-a-development-branchSkill
- gate-checkSkill
- goal-add-minorSkill
- goal-checkSkill
- goal-setSkill
- godot-engineSkill
- helpSkill
- map-systemsSkill
- narrative-designerSkill
- project-stage-detectSkill
- propagate-design-changeSkill
- qa-planSkill
- quick-designSkill
- red-flag-scanSkill
- regression-suiteSkill
- retrospectiveSkill
- review-all-gddsSkill
- safety-pushSkill
- scope-checkSkill
- security-auditSkill
- session-closeSkill
- setup-engineSkill
- sprint-planSkill
- startSkill
- story-doneSkill
- story-readinessSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- team-artSkill
- team-audioSkill
- team-combatSkill
- team-economySkill
- team-infraSkill
- team-levelSkill
- team-marketingSkill
- team-narrativeSkill
- team-polishSkill
- team-releaseSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 29
Read production/workstreams/security.md — what's done, in-progress, next
- Distinctive: line 30
Ask or infer: which ACTIVITY?
- Very specific: line 31
Follow the matching execution chain from team-orchestrator.md
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Team Security
🌱 ShiningPlague-authored. No upstream version exists. Team-orchestrator skill for the security workstream.
Execution protocol: .claude/docs/templates/team-orchestrator.md
Workstream state: production/workstreams/security.md
Domain code: SC
If an artifact named here is absent: say so plainly in one line, skip that step, and continue. Never invent the file to satisfy a checklist, and never fail a close because an optional artifact was never created.
Step 0: Load State + Select Activity
- Read
production/workstreams/security.md— what's done, in-progress, next - Ask or infer: which ACTIVITY? (Design / Build / Content / Playtest / Review / Ship)
- Follow the matching execution chain from
team-orchestrator.md
Agent Routing — WHO to dispatch at each step
| Step in chain | Agent to dispatch | What they do |
| Design: threat model | security-engineer | Vulnerability audit, threat vectors, mitigation spec |
| Design: GDD authoring | security-engineer | Security requirements per system |
| Build: implementation | gameplay-programmer | Save encryption, validation code, input sanitization |
| Build: code review | lead-programmer | Secure coding patterns review |
| Playtest: penetration | security-engineer | Save tampering tests, data manipulation checks |
| Review: code review | lead-programmer | Gate TD-CODE-REVIEW |
Gates to Fire
| Gate | When | Director |
| TD-CODE-REVIEW | After security-related code changes | lead-programmer |
Project-Specific Context
Fill in your threat model (examples):
- Network surface (e.g. single-player offline — no network security needed)
- Primary vectors (e.g. save file tampering, data file manipulation)
- Intentional exposure (e.g. human-editable JSON at
data/exposed on purpose for modding) - Security focus (e.g. save integrity; anti-cheat only if leaderboards ship)
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.