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 agentmods add skills/firstp1ck/pi-coding-agent-forge/vulnerability-scannernpx skills add Firstp1ck/pi-coding-agent-forge --skill vulnerability-scannergit clone --depth 1 https://github.com/Firstp1ck/pi-coding-agent-forgeWhat 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 | $0.00043 | $0.01492 |
| Opus 5 | $0.00022 | $0.00746 |
| Sonnet 5 | $0.00009 | $0.00298 |
| Haiku 4.5 | $0.00004 | $0.00149 |
Grade D, and why
vulnerability-scanner scanned grade D with 3 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 2d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo pacman -S arch-audit Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -sSfL https://raw.githubusercontent.com/anchore/grype/main/install.sh | sh -s -- -b /usr/local/bin Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://<gitea-host>:3000/api/v1/version How it starts
The opening of the file, as written. The whole thing — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vulnerability Scanner
CVE research, system package auditing, and container image vulnerability scanning. Uses web search for CVE lookups and local tools for package/image analysis.
Quick Start
Quick CVE Check for a Specific Software
- Identify the software and version
- Web search:
"[software name] [version] CVE site:nvd.nist.gov OR site:github.com/advisories" - Assess: Is the target version affected?
- Report: Severity, affected versions, fix version, remediation steps
CVE Web Search Workflow
Step 1: Identify Software Versions
Gather current versions of monitored software:
# Docker
docker --version
docker compose version
# System packages (Arch Linux)
pacman -Q <package-name>
# Pi-hole (via SSH or API)
# Check ../workspace-devops/MEMORY.md for known version
# Gitea (via web UI or API)
curl -s http://<gitea-host>:3000/api/v1/version
Step 2: Search for CVEs
Use web search with targeted queries:
| Software | Search Query |
|---|---|
| Pi-hole | "Pi-hole" CVE 2025 2026 vulnerability |
| Gitea | "Gitea" CVE 2025 2026 security advisory |
| Docker | "Docker Engine" CVE 29.2 vulnerability |
| Ollama | "Ollama" CVE vulnerability security |
| OpenClaw | "OpenClaw" CVE vulnerability security |
Useful sources:
- NVD:
site:nvd.nist.gov - GitHub Advisories:
site:github.com/advisories - MITRE:
site:cve.mitre.org - Vendor security pages (e.g.,
blog.gitea.com/security)
Step 3: Assess Impact
For each CVE found:
| Field | Description |
|---|---|
| CVE ID | e.g., CVE-2026-XXXXX |
| CVSS Score | 0.0 - 10.0 |
| Severity | Critical / High / Medium / Low |
| Affected versions | Which versions are vulnerable |
| Target version | What is running |
| Exploitability | Is there a public exploit? |
| Impact | What can an attacker do? |
| Fix version | Which version patches this? |
| Mitigation | Workaround if upgrade isn't immediate |
Step 4: Report
Update MEMORY.md:
- Add to Known Vulnerabilities table if affected
- Update CVE Watch List with last check date
- Log in Audit History
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.
- 2d ago First seen · 244 lines · 43 tokens per session scan D 17ea306f90ed
vulnerability-scanner is a skill published in the GitHub repository Firstp1ck/pi-coding-agent-forge (74 stars, last pushed 3d ago), licensed MIT. It adds 43 tokens to every session and 1,492 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it D with 3 findings (asks for root, downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
flow-nexus-platform
Comprehensive Flow Nexus platform management - authentication, sandboxes, app deployment, payments, and challenges.
github-code-review
Comprehensive GitHub code review with AI-powered swarm coordination.
github-multi-repo
Multi-repository coordination, synchronization, and architecture management with AI swarm orchestration.
github-project-management
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning.
github-workflow-automation
Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management.