Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add wangke19/gemini-ai-helpers --skill codebase-impact-analysisgit clone --depth 1 https://github.com/wangke19/gemini-ai-helpersWrote 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/skills/wangke19/gemini-ai-helpers/codebase-impact-analysis)<a href="https://agentmods.dev/skills/wangke19/gemini-ai-helpers/codebase-impact-analysis"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/codebase-impact-analysis.svg" alt="Measured on agentmods" 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.00030 | $0.01775 |
| Opus 5 | $0.00015 | $0.00888 |
| Sonnet 5 | $0.00006 | $0.00355 |
| Haiku 4.5 | $0.00003 | $0.00178 |
Grade A, and why
Codebase Impact Analysis 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 3d 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.
This is a copy
100% identical to codebase-impact-analysis — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase Impact Analysis
Determines whether a Go codebase is impacted by a specific CVE by applying multiple analysis methods with increasing confidence, collecting evidence, and assigning a risk level.
When to Use This Skill
Use this skill when:
- A CVE profile has been gathered (from the cve-intelligence-gathering skill)
- You need to determine if the current Go project is affected
- You need to assign a risk level with supporting evidence
Prerequisites
Required Tools (validated in Phase 0 of parent command)
gotoolchain withgo.modin workspace rootgovulncheck:go install golang.org/x/vuln/cmd/govulncheck@latestcallgraph:go install golang.org/x/tools/cmd/callgraph@latestdigraph:go install golang.org/x/tools/cmd/digraph@latest
Required Inputs
From Phase 1 (CVE Intelligence Gathering skill):
- CVE ID
- Affected package/module name(s)
- Vulnerable version range
- Fixed version (if available)
- Vulnerable function signatures (if known)
From Parent Command:
--algopreference for call graph analysis (default:vta)
Implementation Steps
Step 1: Identify Go Module Dependencies
# Parse dependencies from go.mod
go list -m all
# Get detailed dependency info
go list -m -json all
- Read
go.modfrom workspace root - Parse direct and indirect dependencies
- Extract module versions
Step 2: Cross-Reference Vulnerable Packages
Apply the following methods in order. Each provides increasing confidence.
Method 1: Dependency Matching
- Compare CVE-affected packages with
go.moddependencies - Check if affected package versions are in use
- Account for version ranges and semantic versioning
# Check if vulnerable package is a dependency
go list -m <vulnerable-package>
Decision Point:
- IF package NOT in dependencies → Skip to risk assignment (likely LOW RISK)
- IF package found → Continue to Method 2
Method 2: Go Vulnerability Scanner
# Run official Go vulnerability scanner
govulncheck ./...
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.
- 3d ago First seen · 221 lines · 30 tokens per session scan A 182156df016d
Codebase Impact Analysis is a skill published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 1,775 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to codebase-impact-analysis, differing in 4 lines, and is treated as a copy.
Other skills, from other repositories
mongodb-query-optimizer
Help with MongoDB query optimization and indexing. Use only when the user asks for optimization or performance: "How do I optimize this query?", "How do I index this?", "Why is this query slow?", "Can you fix my slow queries?", "What are the slow queries on my cluster?", etc. Do not invoke for general MongoDB query…
lov-article-creator
A skill that turns source material or a draft into a complete, branded WeChat public-account article package.
lov-bp-outline
A process for turning project information into a source-backed business-plan brief, evidence record, and 12–15-slide outline. A business plan explains how a company works, grows, and makes money.
recon-dir-scan
Directory and file enumeration using ffuf, gobuster, dirsearch, and feroxbuster. Use this skill when user needs to discover hidden directories, enumerate files, find backup files, or map application structure through path fuzzing.
18f-content
Draft, rewrite, or audit inclusive US digital-government content using an independently expressed interpretation of the 18F Content Guide. Use for public-service websites, forms, applications, transactional messages, help content, notices, and government digital experiences that should help people complete a task with…
convert-to-devto
Converts Markdown content into the format required for Dev.to publication, ensuring correct YAML frontmatter, headers, liquid tags, and inline formatting. Use when the user asks to format or convert an existing blog post or Markdown file for Dev.to.