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.
4 critical findings reported by cisco-skill-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 -- gahshsfshsh/luzhniki
4 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.
v2.0.11
11 findings · 8.1s
v0.3.74
1 finding · 0.9s
v0.1.0
0 findings · 3.3s
v0.1.0
0 findings · 3.3s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
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 · 0.8s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 22, 2026 | Scan Halted | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicable | rejected |
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 12 findings across every scanner that examined this package. 2 of 4 findings rated critical by their scanner were 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.
2 Placeholder value — The matched literal is a placeholder or example — the kind of value a scanner reads as a secret and a human reads as a blank to fill in.
Rules: YARA_credential_harvesting_generic · Files: /repo/CREATE_GITHUB_TOKEN.md · reported by cisco-skill-scanner
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.
2 HIDDEN_DATA_FILE
Files: /repo/apps/mobile/.run/main.xml, /repo/apps/mobile/.metadata · reported by cisco-skill-scanner
2 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md, /repo/packages/backend/SKILL.md · reported by cisco-skill-scanner
2 SECRET_GITHUB_TOKEN
Files: /repo/SKILL.md · reported by cisco-skill-scanner
2 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/packages/backend/SKILL.md · reported by cisco-skill-scanner
1 AAK-LEGAL-002
Files: packages/backend/package.json · reported by agent-audit-kit
1 LOW_ANALYZABILITY
Files: /repo/packages/backend · reported by cisco-skill-scanner
Artifact exposes GitHub tokens, posing a critical credential risk.
The artifact contains exposed GitHub tokens within the `/repo/SKILL.md` file. This credential exposure could enable unauthorized access to external resources or services. Such access might include reading or writing to repositories, or interacting with other GitHub-integrated systems.
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.