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 NOMARJ/sigil --skill supply-chain-auditgit clone --depth 1 https://github.com/NOMARJ/sigilWrote 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/nomarj/sigil/supply-chain-audit)<a href="https://agentmods.dev/skills/nomarj/sigil/supply-chain-audit"><img src="https://agentmods.dev/badge/skills/nomarj/sigil/supply-chain-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/skills/nomarj/sigil/supply-chain-audit"><img src="https://agentmods.dev/badge/skills/nomarj/sigil/supply-chain-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.00072 | $0.00699 |
| Opus 5 | $0.00036 | $0.00349 |
| Sonnet 5 | $0.00014 | $0.00140 |
| Haiku 4.5 | $0.00007 | $0.00070 |
Grade A, and why
supply-chain-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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Supply Chain Risk Auditor
Adapted from Trail of Bits' supply-chain-risk-auditor skill. Evaluates the security posture of project dependencies because your app is only as secure as its weakest dependency.
What You're Auditing
Known Vulnerabilities
- Check dependencies against known CVE databases
- Run
npm audit,pip-audit,cargo audit,govulncheckas appropriate - Flag severity: Critical, High, Medium, Low
- Check if patches are available
Dependency Health Signals
For each significant dependency, assess:
- Maintenance status: Last commit date, release frequency, open issue count
- Maintainer count: Single maintainer = bus factor risk
- Download/usage stats: Very low usage for a critical function = suspicious
- License compatibility: Does the license work with your project?
Supply Chain Attack Vectors
- Typosquatting: Does this package name closely resemble a popular package? (
lodashvsl0dash) - Dependency confusion: Could an internal package name collide with a public one?
- Compromised maintainer: Has the package ownership changed recently?
- Install scripts: Does the package run code during
npm install/pip install? - Excessive permissions: Does a "color formatting" library need network access?
Dependency Hygiene
- Version pinning: Are versions pinned or floating? (Floating = you auto-adopt compromised releases)
- Lock file integrity: Is the lock file committed and up to date?
- Transitive depth: How deep is the dependency tree? Each level adds risk.
- Unused dependencies: Dependencies that aren't imported but are installed = unnecessary attack surface
Audit Protocol
1. Identify dependency files in the change set
2. Run automated vulnerability scanning (npm audit, pip-audit, etc.)
3. For new/changed dependencies:
a. Check package registry for health signals
b. Review install scripts
c. Check for typosquatting indicators
d. Assess maintenance status
4. Classify findings by severity
5. Recommend: update, replace, or accept with justification
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.
- 5d ago First seen · 72 lines · 72 tokens per session scan A 2920c405e660
supply-chain-audit is a skill published in the GitHub repository NOMARJ/sigil (5 stars, last pushed 4d ago), licensed Apache-2.0. It adds 72 tokens to every session and 699 once invoked, about $0.0004 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-09-04.
Other skills, from other repositories
sftp-cc
A natural-language SFTP tool for uploading local project files to a remote server. SFTP is a secure way to transfer files, and this tool supports incremental uploads, private-key binding, and permission fixes.
regex-mastery
Use this skill when writing regular expressions, debugging pattern matching,optimizing regex performance, or implementing text validation. Triggers on regex, regular expressions, pattern matching, lookahead, lookbehind, named groups, capture groups, backreferences, and any task requiring text pattern matching.
devtools-event-client
Create typed EventClient for a library. Define event maps with typed payloads, pluginId auto-prepend namespacing, emit()/on()/onAll()/onAllPluginEvents() API. Connection lifecycle (5 retries, 300ms), event queuing, enabled/disabled state, SSR fallbacks, singleton pattern. Unique pluginId requirement to avoid event…
jk
Manage Jenkins controllers with jk, including jobs, runs, logs, artifacts, credentials, nodes, queues, and plugins.
assess-patch-risk
Assess an immutable patch artifact's program impact, regression risk, and auto-merge eligibility. Use for generated patch files, provider pull-request diffs, or commit ranges when reviewers need evidence about affected runtime paths, contracts, tests, and recoverability. This skill is read-only and does not generate…
market-sizing
TAM/SAM/SOM market sizing analysis. Uses web search and research tools to produce a structured analysis with data sources, assumptions, calculations, and confidence ranges. Triggers on: "calculate TAM", "size the market", "market opportunity".