LeanMeanCleanAppsLeanMeanCleanApps/CleanModelContextProtocol/.agents/skills/security-findings/SKILL.mdsecurity-findings
Skill1 starsChanged 7 days agoMITView on GitHub
How to handle CodeQL, Trivy, Dependency Review and secret scanning findings - fixing them, when a dismissal or .trivyignore entry is acceptable, and who decides. Use when a security check fails or a code scanning alert is raised.
In this repository40 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-a-use-caseSkill
- api-conventionsSkill
- branches-and-pull-requestsSkill
- cancellationSkill
- ci-for-your-solutionSkill
- ci-pipelineSkill
- clean-architecture-layersSkill
- configuration-and-environmentsSkill
- coverageSkill
- csharp-house-styleSkill
- data-access-ef-coreSkill
- database-migrationsSkill
- docker-and-composeSkill
- docs-and-voiceSkill
- errors-and-exceptionsSkill
- expose-a-use-caseSkill
- family-syncSkill
- health-checksSkill
- integration-testsSkill
- json-serializationSkill
- mapping-with-mapperlySkill
- mcp-inspectorSkill
- mediatorSkill
- optional-token-authSkill
- packages-and-dependenciesSkill
- pagingSkill
- presentation-integration-testsSkill
- releasesSkill
- sample-dataSkill
- serilogSkill
- telemetrySkill
- template-authoringSkill
- test-designSkill
- time-providerSkill
- unit-testsSkill
- validationSkill
- writing-a-skillSkill
- xml-docs-and-openapiSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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
- Distinctive: line 25
Read the finding and confirm it applies.
- Very specific: line 27
If no fix exists yet (an unfixed OS package), Trivy's ignore-unfixed already skips it.
- Distinctive: line 28
When the maintainer accepts a risk, record the reason where the table says, in the same pull request.
- Distinctive: line 34
Commit a secret, even to a branch, even briefly.
≈ “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
Security findings
The rule
Security checks report and block; people decide. A finding is fixed in code whenever a fix exists. Only the maintainer dismisses an alert or accepts a risk, and every accepted risk has a written reason next to it.
| Tool | Finds | Where the reason goes if it's accepted |
| CodeQL | Code and workflow weaknesses | The alert's dismissal comment ("won't fix" with why) |
| Trivy | Vulnerable OS or .NET packages in the image, Dockerfile and compose misconfiguration | .trivyignore, one id per line with a comment above it |
| Dependency Review | Vulnerable or wrongly licensed packages added in a pull request | Not dismissible; change the package |
| Secret scanning and push protection | Credentials in commits | Not dismissible; rotate the secret and remove it |
Private vulnerability reports arrive through SECURITY.md, never as public issues.
Steps
- Read the finding and confirm it applies. A CodeQL "missing authorization" on an endpoint that's meant to be anonymous is a real decision, not noise.
- Fix it: update the package or base image, change the code, tighten the config.
- If no fix exists yet (an unfixed OS package), Trivy's
ignore-unfixedalready skips it. If a fix exists but can't be taken, ask the maintainer. - When the maintainer accepts a risk, record the reason where the table says, in the same pull request.
Don't
- Dismiss an alert or add a
.trivyignoreentry yourself. - Lower a severity threshold or remove a scanner.
- Commit a secret, even to a branch, even briefly.
- Discuss an unfixed vulnerability in a public issue or pull request.
Check
Static Analysis and Container Scan are green, and the repository's Security tab shows no new open alerts.
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.