Loading the registry…
Practical design patterns, protocols, and architectures for real-world AI agents
Cursor Rules are .cursorrules / .cursor/rules files that steer Cursor's AI; scanned with the same pipeline.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
3 critical findings reported by agent-audit-kit, osv-scanner, 2 of them in the installed artifact. The composite score alone does not reflect this — read the per-scanner reports below.
Cursor Rules are .cursorrules / .cursor/rules files that steer Cursor's AI. Review the scanned source before copying them into your own project.
nerlo install -- agent-patterns-lab
7 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v1.4.0
2 findings · 0.6s
v2.0.11
37 findings · 9.6s
v0.3.74
47 findings · 4.5s
v0.1.0
0 findings · 3.7s
v0.1.0
0 findings · 3.7s
v0.71.0
0 findings · 0.3s
v2.3.8
71 findings · 1.5s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 1.8s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.1s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 21, 2026 | Flagged62 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicabletrivy: completeosv-scanner: completetrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
Out of 157 findings across every scanner that examined this package. 1 of 3 findings rated critical by their scanner was among the dismissals.
Two keys had to turn. The model had to name a reason from a fixed list of six, and a deterministic check of ours — over which files this artifact actually installs — had to independently agree. Anything it could not corroborate is in “not reviewed” above, at full severity.
17 Agent instruction file — The match is in a file that instructs an AI coding agent — a CLAUDE.md or similar. It is documentation of intent, and our own check confirmed it is not part of what gets installed.
Rules: TOOL_ABUSE_UNDECLARED_NETWORK, SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE and 1 more · Files: /repo/repo/AGENTS.md, /repo/examples/02-mcp-tool-integration/repo/examples/02-mcp-tool-integration/README.md, /repo/examples/03-checkpoint-recovery/repo/examples/03-checkpoint-recovery/README.md and 6 more · reported by cisco-skill-scanner
10 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: AAK-SSRF-001, RESOURCE_ABUSE_INFINITE_LOOP, AAK-MCP-HTTP-NOAUTH-SERVER-001 and 3 more · Files: examples/03-checkpoint-recovery/src/mcp_servers/crypto_intelligence.py, /repo/examples/03-checkpoint-recovery/src/agents/research_planner.py, examples/02-mcp-tool-integration/src/mcp_servers/crypto_intelligence.py and 2 more · reported by agent-audit-kit, cisco-skill-scanner
6 CI or editor configuration — The match is in build, CI or editor configuration, confirmed by our own check to be outside the installed artifact.
Rules: AAK-GHA-IMMUTABLE-001 · Files: .github/workflows/deploy.yml, .github/workflows/ci.yml, .github/workflows/security.yml · reported by agent-audit-kit
1 Test or fixture file — The match is in a test or fixture. Our own check confirmed the file is not part of what gets installed.
Rules: AAK-TASKS-003 · Files: examples/03-checkpoint-recovery/tests/unit/test_mcp_tools.py · reported by agent-audit-kit
These findings are in files this artifact installs and are not placeholder values. No false-positive basis can be corroborated for such a finding, so this review never dismisses one; they were not sent to the model and stand at their scanner's severity.
11 MANIFEST_MISSING_LICENSE
Files: /repo/.cursor/skills/engineering-tracker/SKILL.md, /repo/.cursor/skills/tester/SKILL.md, /repo/.cursor/skills/runtime-verifier/SKILL.md and 8 more · reported by cisco-skill-scanner
10 AAK-MCP-ATTEST-001
Files: .cursor/mcp.json · reported by agent-audit-kit
6 AAK-MCP-007
Files: .cursor/mcp.json · reported by agent-audit-kit
6 AAK-SUPPLY-001
Files: .cursor/mcp.json · reported by agent-audit-kit
5 AAK-MCP-005
Files: .cursor/mcp.json · reported by agent-audit-kit
2 HIDDEN_DATA_FILE
Files: /repo/.pre-commit-config.yaml, /repo/.secrets.baseline · reported by cisco-skill-scanner
Critical vulnerabilities and supply chain risks detected
The artifact contains critical vulnerabilities (PYSEC-2026-36, PYSEC-2026-2102) in its dependencies, as indicated in `/repo/uv.lock`. High-severity findings include multiple supply chain risks (AAK-SUPPLY-001) within `.cursor/mcp.json`. Potential server-side request forgery (AAK-LANGCHAIN-SSRF-REDIR-001) and injection vulnerabilities (AAK-MCP-STDIO-LAUNCHER-INJECT-001) are present in `uv.lock` and `.cursor/mcp.json` respectively. Additionally, `settings.local.json` lacks a deny-list for permissions, and numerous other high-severity dependency vulnerabilities are present.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.
1 AAK-LANGCHAIN-SSRF-REDIR-001
Files: uv.lock · reported by agent-audit-kit
1 AAK-MCP-006
Files: .cursor/mcp.json · reported by agent-audit-kit
1 AAK-MCP-LANGGRAPH-CHECKPOINT-CVE-2026-71433-001
Files: uv.lock · reported by agent-audit-kit
1 AAK-MCP-SDK-CVE-2026-52869-001
Files: uv.lock · reported by agent-audit-kit
1 AAK-MCP-STDIO-LAUNCHER-INJECT-001
Files: .cursor/mcp.json · reported by agent-audit-kit
1 AAK-SSRF-TOCTOU-001
Files: uv.lock · reported by agent-audit-kit
1 AAK-TRUST-004
Files: .claude/settings.local.json · reported by agent-audit-kit
1 AAK-TRUST-006
Files: .claude/settings.local.json · reported by agent-audit-kit
1 EXCESSIVE_FILE_COUNT
Files: /repo/. · reported by cisco-skill-scanner
1 GHSA-4xgf-cpjx-pc3j
Files: /repo/uv.lock · reported by osv-scanner
1 GHSA-537c-gmf6-5ccf
Files: /repo/uv.lock · reported by osv-scanner
1 GHSA-f4xh-w4cj-qxq8
Files: /repo/uv.lock · reported by osv-scanner
1 GHSA-jq35-7prp-9v3f
Files: /repo/uv.lock · reported by osv-scanner
1 hooks-no-pretooluse
Files: settings.local.json · reported by agentshield
1 permissions-no-deny-list
Files: settings.local.json · reported by agentshield
1 PYSEC-2026-141
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-142
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-161
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-175
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-177
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-178
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-179
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1845
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2094
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2095
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2096
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2097
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2098
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2099
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2100
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2101
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2102
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2103
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2104
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2105
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2106
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2107
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2108
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2109
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2110
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2111
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2112
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2113
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2132
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-215
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2193
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2275
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2280
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2281
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-237
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-248
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-249
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2556
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2560
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2563
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2564
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2573
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2575
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2582
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2583
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2987
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3036
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3037
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3038
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3039
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3040
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3041
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3481
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3482
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3483
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-35
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3545
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3546
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3547
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3552
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3553
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3554
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-36
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3635
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-76
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-77
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-87
Files: /repo/uv.lock · reported by osv-scanner
1 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md · reported by cisco-skill-scanner
Showing 25 of 47; the rest are in the per-scanner reports above.