security-review
Skill1 starsChanged 17 days agoMITView on GitHub
Review changed MuseFlow code for security vulnerabilities and audit dependencies. Use before opening a PR that touches authentication, API endpoints, external API adapters or settings.
191 other projects use a version of this.
Adopted by
Most recently taken up by
- Badhon-00/MDCPtheir own version, first seen Nov 16, 2026
- FAHTHIZ/oasistheir own version, first seen Nov 16, 2026
- metacircu1ar/hive_skillstheir own version, first seen Nov 15, 2026
- rschuft/ai-frontend-skill-packstheir own version, first seen Nov 15, 2026
- 81wallace18/codex-skillstheir own version, first seen Nov 15, 2026
- FimawLLC/fimaw-skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use linkerd-patterns, dependency-cve-sweep and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
xfstudioSkilllinkerd-patterns
Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments. Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking with minimal overhead.
Also in 5 projects that use this
berntpoppSkilldependency-cve-sweep
Use when handling Dependabot PRs, CodeQL/Trivy alerts, or doing a routine dependency/CVE sweep for this repo.
Also in 12 projects that use this
berntpoppSkillfleet-standard-adoption
Use when bringing this repo into compliance with a GeneFoundry fleet standard (tool-naming, response-envelope, container-hardening, versioning, MCP transport, or logging) or closing its tracking issue.
Also in 12 projects that use this
HABUBUSSSkillproject-guidelines-example
Also in 16 projects that use this
niloykumarbarmanSkillagent-sort
Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.
Also in 13 projects that use this
royaluniondesign-sysSkillconfigure-ecc
Interactive installer for Everything Claude Code — guides users through selecting and installing skills and rules to user-level or project-level directories, verifies paths, and optionally optimizes installed files.
Also in 11 projects that use this
- +2 more from berntpopp
Other versions191 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 191
- affaan-m/ECC★ 246ksame name
- github/awesome-copilot★ 41ksame name
- langfuse/langfuse★ 37ksame name
- nearai/ironclaw★ 13ksame name
- joe-bell/cva★ 6.9ksame name
- doorkeeper-gem/doorkeeper★ 5.5ksame name
- github/squad★ 3.4ksame name
- compozy/compozy★ 2.9ksame name
- trycompai/comp★ 2.1ksame name
- xu-xiang/everything-claude-code-zh★ 1.9ksame name
181 more not listed
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 repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- migrations/AGENTS.mdAGENTS.md
- tests/AGENTS.mdAGENTS.md
- arch-reviewSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 1 is distinctive, and 6 are very specific to this project.
0
Common
Most of the 164 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
If no files are given above, review the branch: git diff --name-only origin/main...HEAD plus the uncommitted changes from git status …
- Distinctive: line 29
No hardcoded credentials, API keys, tokens or passwords.
- Very specific: line 30
No secrets in logs (user_id, status_code, provider are fine) or in API responses (raw OAuth tokens, hashes).
- Very specific: line 33
Every protected endpoint depends on get_current_user.
- Very specific: line 45
No raw SQL built from user values (f-strings, .format(), %).
- Very specific: line 48
Every httpx client has a timeout.
- Very specific: line 59
Run uv audit. For each CVE, give its severity and whether the vulnerable code path is reachable here.
“Common” is measured: kept by at least 6 in 10 of the 164 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
You are a security engineer reviewing MuseFlow code. You report vulnerabilities; you do not fix them.
Scope
- Files to review: $ARGUMENTS
- If no files are given above, review the branch:
git diff --name-only origin/main...HEADplus the uncommitted changes fromgit status --short.
Context
- API: FastAPI, JWT verified by the
get_current_userdependency. - OAuth: Spotify flow with single-use state tokens, consumed through the
consume_oauth_stateuse case in theget_user_from_statedependency. - DB: PostgreSQL through SQLAlchemy, accessed by use cases through the unit of work.
- External APIs: Spotify and OpenRouter through httpx with tenacity retries.
- Secrets: Pydantic
BaseSettings, from environment variables only.
Checklist
Secrets
- No hardcoded credentials, API keys, tokens or passwords; secrets come from settings only.
- No secrets in logs (
user_id,status_code,providerare fine) or in API responses (raw OAuth tokens, hashes).
Authentication and authorization
- Every protected endpoint depends on
get_current_user; no manualjwt.decode()in a route. /registerand/loginare public on purpose: their errors must not reveal whether a user exists.- The OAuth callback uses
get_user_from_state, which validates and consumes the state before anything else; a state is never reusable and expires afterOAUTH_STATE_TTL_SECONDS.
Input validation
- API input goes through Pydantic models (no raw
request.body()or dict parsing); CLI input through typed Typer parameters and input schemas. - User-supplied file paths go through
pathlib.Path; noopen(str_from_user), no shell interpolation. - Numeric options (
--batch-size,--limit) have explicitmin/maxbounds.
SQL
- No raw SQL built from user values (f-strings,
.format(),%); ORM constructs ortext()with bound parameters.
External APIs
- Every httpx client has a timeout; SSL verification is never disabled (
verify=False). Retry-Afteris checked againstmax_retry_waitbefore sleeping;ProviderRateLimitExceededErroris raised, not swallowed, when it exceeds the maximum.
Error handling and leakage
- HTTP error responses carry no stack trace or raw internal exception message.
- CLI commands show
str(e)to the user; the traceback goes to the logger withlogger.exception(). - Allowed:
{e}in a log message when the detail is deliberate operator diagnostics (e.g. skipped items in a long CLI run).
Dependencies
Run uv audit. For each CVE, give its severity and whether the vulnerable code path is reachable here.
Output
For each issue: file and line, the offending code, the risk (CWE / OWASP category when relevant), and the fix.
Severities: [CRITICAL] exploitable (auth bypass, secret exposure, injection), [HIGH] exploitable under some
conditions, [MEDIUM] harder to exploit but real, [LOW] defense in depth, [INFO] observation.
Then run make lint and report its result. Conclude with the highest severity, the totals per level and a verdict:
SECURE or ISSUES FOUND.
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.

