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 Firstp1ck/pi-coding-agent-forge --skill code-securitygit clone --depth 1 https://github.com/Firstp1ck/pi-coding-agent-forgeWrote 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/firstp1ck/pi-coding-agent-forge/code-security)<a href="https://agentmods.dev/skills/firstp1ck/pi-coding-agent-forge/code-security"><img src="https://agentmods.dev/badge/skills/firstp1ck/pi-coding-agent-forge/code-security/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/skills/firstp1ck/pi-coding-agent-forge/code-security"><img src="https://agentmods.dev/badge/skills/firstp1ck/pi-coding-agent-forge/code-security.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 7 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 18 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 73 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 121 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 23 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 101 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 105 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Tool Misuse · line 211 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00048 | $0.02190 |
| Opus 5.5 | $0.00019 | $0.00876 |
| Sonnet 5.5 | $0.00010 | $0.00438 |
| Haiku 4.5 | $0.00005 | $0.00219 |
Grade A, and why
code-security scanned grade A with 1 finding 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
os.system(user_input) How it starts
The opening of the file, as written. The whole thing — 319 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Security
Secret scanning, dependency vulnerability auditing, static analysis patterns, and supply chain security for the user's codebases.
Quick Start
Quick Repo Security Check
Run these in order for any repository:
# 1. Check for leaked secrets
grep -rn "sk-proj-\|sk-\|AKIA\|ghp_\|gho_\|github_pat_\|xoxb-\|xoxp-" --include="*.py" --include="*.ts" --include="*.js" --include="*.rs" --include="*.sh" --include="*.toml" --include="*.json" --include="*.yml" --include="*.yaml" --include="*.env" .
# 2. Check .gitignore covers sensitive files
cat .gitignore | grep -i "env\|secret\|key\|token\|credential"
# 3. Check for .env files in repo
find . -name ".env*" -not -path "./.git/*"
# 4. Run dependency audit (language-specific)
cargo audit # Rust
npm audit # JavaScript/TypeScript
pip-audit # Python (via pip install pip-audit)
Secret Scanning
Patterns to Detect
| Pattern | Regex | Severity |
|---|---|---|
| OpenAI API key | sk-proj-[A-Za-z0-9_-]{20,} |
Critical |
| OpenAI legacy key | sk-[A-Za-z0-9]{20,} |
Critical |
| AWS access key | AKIA[0-9A-Z]{16} |
Critical |
| GitHub PAT | ghp_[A-Za-z0-9]{36} |
Critical |
| GitHub OAuth | gho_[A-Za-z0-9]{36} |
Critical |
| GitHub App token | github_pat_[A-Za-z0-9_]{22,} |
Critical |
| Slack token | xox[bpors]-[A-Za-z0-9-]{10,} |
High |
| Telegram bot token | [0-9]{8,10}:AA[A-Za-z0-9_-]{33} |
High |
| Discord bot token | [MN][A-Za-z0-9]{23,}\.[A-Za-z0-9_-]{6}\.[A-Za-z0-9_-]{27,} |
High |
| JWT token | eyJ[A-Za-z0-9_-]*\.eyJ[A-Za-z0-9_-]*\.[A-Za-z0-9_-]* |
High |
| Generic API key | [Aa]pi[_-]?[Kk]ey.*[=:]\s*["'][A-Za-z0-9]{20,} |
Medium |
| Password in URL | ://[^:]+:[^@]+@ |
High |
| Private key header | `-----BEGIN (RSA | EC |
| Password assignment | [Pp]assword\s*[=:]\s*["'][^"']{8,} |
High |
Manual Secret Scan
# Comprehensive secret scan across a repo
grep -rn \
-e "sk-proj-" \
-e "sk-[A-Za-z0-9]\{20,\}" \
-e "AKIA[0-9A-Z]\{16\}" \
-e "ghp_" \
-e "gho_" \
-e "github_pat_" \
-e "xox[bpors]-" \
-e "BEGIN.*PRIVATE KEY" \
-e "password\s*=" \
-e "api_key\s*=" \
-e "secret\s*=" \
--include="*.py" --include="*.ts" --include="*.js" --include="*.rs" \
--include="*.sh" --include="*.toml" --include="*.json" --include="*.yml" \
--include="*.yaml" --include="*.env" --include="*.cfg" --include="*.ini" \
.
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 · 319 lines · 48 tokens per session scan A f605db3cb233
code-security is a skill published in the GitHub repository Firstp1ck/pi-coding-agent-forge (91 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 2,190 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
convex-component-authoring
How to create, structure, and publish self-contained Convex components with proper isolation, exports, and dependency management.
npm-docs
Use this skill whenever the user asks about npm, package management, publishing packages, semantic versioning, npm CLI commands, or Node.js dependencies. Covers npm 12.x including the registry, scopes, organizations, security (audit, provenance, 2FA), CI/CD integration, workspaces, scripts, .npmrc configuration, and…
convex-component-authoring
How to create, structure, and publish self-contained Convex components with proper isolation, exports, and dependency management.
dependency-manager
Manage project dependencies — update packages, audit vulnerabilities, resolve conflicts, and keep dependencies healthy. Use when updating packages, fixing vulnerability alerts, or resolving dependency issues.
colab-finetuning
Fine-tune LLMs on Google Colab GPUs directly from openscience. Connects to Colab runtimes via WebSocket bridge for remote training with Unsloth. Supports SFT, GRPO, DPO, vision, and TTS workflows on free T4 to Pro A100 GPUs.
swarm-pr-review
Run a graph-guided, tool-augmented PR review using context packing, parallel exploration, mandatory repository-agnostic risk-family coverage with dispatch scaled to diff size and risk, independent reviewer validation, critic challenge, and metrics writeback. Use for deep pull request review with low false-positive…