Borrowing it
Nothing to install: this file belongs to Nano-Nimbus/locus. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Nano-Nimbus/locus/main/.github/prompts/gemini-security-audit.mdgit clone --depth 1 https://github.com/Nano-Nimbus/locusWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/nano-nimbus/locus/gemini-security-audit)<a href="https://agentmods.dev/commands/nano-nimbus/locus/gemini-security-audit"><img src="https://agentmods.dev/badge/commands/nano-nimbus/locus/gemini-security-audit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/nano-nimbus/locus/gemini-security-audit"><img src="https://agentmods.dev/badge/commands/nano-nimbus/locus/gemini-security-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00365 |
| Opus 5.5 | $0.00000 | $0.00146 |
| Sonnet 5.5 | $0.00000 | $0.00073 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
gemini-security-audit scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Gemini Code Assist GitHub Action Prompt: Security Audit + Reporting
You are running in GitHub Actions. Execute a full security audit pass and generate auditable artifacts.
Workflow
- Install dependencies:
uv sync --extra dev
- Run unit tests:
uv run pytest tests/unit/ -v --tb=short
- Run security tooling:
mkdir -p docs/audits/artifactsuv run --with bandit bandit -r locus -f json -o docs/audits/artifacts/gemini-bandit.json || trueuv run --with pip-audit pip-audit > docs/audits/artifacts/gemini-pip-audit.txt 2>&1 || true
- Manually review exploitability and attack vectors in:
locus/mcp/locus/agent/.github/workflows/- dependency configuration (
pyproject.toml,uv.lock)
Deliverables
Write:
docs/audits/gemini-security-pr-review-report.mddocs/audits/gemini-security-pr-comment.md
Full Report Schema
- Executive summary
- Scope and methodology
- Scanner results summary
- Findings by severity
- For each finding:
- ID
- Severity
- Location with line numbers
- Evidence
- Exploit narrative
- Impact
- Fix recommendation
- Temporary mitigation
- Final merge recommendation
Output Discipline
- Be explicit about uncertainty.
- Do not overstate scanner output.
- If no major issues are found, still include residual risks and hardening suggestions.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 50 lines · 0 tokens per session scan A 83da7b0ba5b0
gemini-security-audit is a command published in the GitHub repository Nano-Nimbus/locus (0 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 365 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-08.
Other commands, from other repositories
test-tdd
Run when user calls /test-tdd. Scans modified files, locates their corresponding unit/integration test suites, and runs them.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
lg:node
Create, modify, and manage nodes in LangGraph graphs including LLM nodes, tool nodes, human-in-the-loop, subgraphs, and conditional nodes.
test-audit
Writes a versioned TESTAUDIT.md; with --fix, quarantines the rot in gated, revertible commits. TRIGGER WHEN: auditing a test suite, measuring test health, finding dead or flaky or redundant tests, or diagnosing failure causes and proposing temporary quarantine. DO NOT TRIGGER WHEN: one module's tests are consolidated…
story-and-test
For the component(s) in scope.
test
Execute a comprehensive test run for the following target.