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 jmylchreest/aide --skill semgrepgit clone --depth 1 https://github.com/jmylchreest/aideWrote 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/jmylchreest/aide/semgrep)<a href="https://agentmods.dev/skills/jmylchreest/aide/semgrep"><img src="https://agentmods.dev/badge/skills/jmylchreest/aide/semgrep/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/jmylchreest/aide/semgrep"><img src="https://agentmods.dev/badge/skills/jmylchreest/aide/semgrep.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00011 | $0.00460 |
| Opus 5 | $0.00005 | $0.00230 |
| Sonnet 5 | $0.00002 | $0.00092 |
| Haiku 4.5 | $0.00001 | $0.00046 |
Grade A, and why
semgrep 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 9d 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
Semgrep Security Analysis
Run Semgrep to detect security vulnerabilities and code quality issues in the codebase.
Workflow
1. Run Semgrep scan
# Auto-detect rules for the project's languages
semgrep scan --config auto --json --quiet 2>/dev/null | head -c 50000
If JSON output is too large, use text output:
semgrep scan --config auto --quiet 2>/dev/null
2. For specific rule sets
# Security-focused rules only
semgrep scan --config "p/security-audit" --json --quiet
# OWASP Top 10
semgrep scan --config "p/owasp-top-ten" --json --quiet
# Language-specific
semgrep scan --config "p/golang" --json --quiet
semgrep scan --config "p/python" --json --quiet
semgrep scan --config "p/typescript" --json --quiet
3. Triage results
For each finding:
- Read the file and surrounding context
- Assess whether the finding is a true positive or false positive
- For true positives, fix the issue following the suggestion in the finding
- For false positives, consider adding a
# nosemgrepinline comment with justification
4. Scan specific files
# Scan only changed files
semgrep scan --config auto --json --quiet -- path/to/file.py
Common Issues
- Too many findings: Use
--severity ERRORto focus on critical issues first - Slow scan: Use
--config autoinstead of multiple rule packs to avoid re-scanning - Missing rules: Install additional rules with
semgrep registry - False positives: Add
# nosemgrep: rule-idwith a comment explaining why
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.
- 9d ago First seen · 71 lines · 11 tokens per session scan A f97657c1fcce
semgrep is a skill published in the GitHub repository jmylchreest/aide (17 stars, last pushed 2d ago), licensed MIT. It adds 11 tokens to every session and 460 once invoked, about $0.0001 per session on Opus 5. 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-08-30.
Other skills, from other repositories
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
find-simplifications
Use for a periodic repo-wide sweep of qwen-code for accumulated excess surface — dead components and files, orphaned locale keys, exports nothing consumes, added-then-removed scaffolding — filing candidates on a tracking issue and landing only what a maintainer has said yes to. Repo-wide and evidence-first; every…
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…
bundle-safety
Bundle transform safety — minification variant selection, consumer-constraint verification, identifier preservation, and namespace re-export coverage for build output.
safe-extraction
Apply when extracting code from a large monolith file into submodules. Covers barrel re-exports, internals DI seam proxy patterns, CI invariant allowlist updates, and cross-file test verification. Prevents CI failures, broken imports, and test regressions from code extraction.
durable-session-state
Persist plans, scope decisions, evidence, and reviewer/critic verdicts to durable files during long or multi-phase tasks so work survives context compaction, session resumes, and handoffs. Use for swarm-mode tasks, before context grows large, when recording approval gates, and when resuming after compaction or a…