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/richfrem/agent-plugins-skills/path-reference-auditornpx skills add richfrem/agent-plugins-skills --skill path-reference-auditorgit clone --depth 1 https://github.com/richfrem/agent-plugins-skillsWrote 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/richfrem/agent-plugins-skills/path-reference-auditor)<a href="https://agentmods.dev/skills/richfrem/agent-plugins-skills/path-reference-auditor"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/path-reference-auditor.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 | $0.00096 | $0.01938 |
| Opus 5 | $0.00048 | $0.00969 |
| Sonnet 5 | $0.00019 | $0.00388 |
| Haiku 4.5 | $0.00010 | $0.00194 |
Grade A, and why
path-reference-auditor 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 yesterday.
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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependencies
This skill requires Python 3.8+ and standard library only. No external packages needed.
To install this skill's dependencies:
pip-compile ./requirements.in
pip install -r ./requirements.txt
See requirements.txt for the dependency lockfile (currently empty — standard library only).
Path Reference Auditor
Complete path reference audit system for plugins and skills. Ensures all ./file references in code actually exist.
What This Skill Does
Validates that file references in plugins and skills are:
- Skill-local: References in
.agents/skills/Y/stay withinY/ - Plugin-local: References in
plugins/X/(root level) stay withinX/ - Resolvable: All
./paths point to actual files (or symlinks)
Generates an inventory.json database of all references for reuse in multiple checks.
Three-Phase Audit
Phase 1: SCAN
Find all ./reference patterns in .py, .md, .mmd, .json, .sh files.
Populates temp/inventory.json with raw reference data.
python ./scripts/path_reference_auditor.py --project . --phase scan
Output: temp/inventory.json with all references found
Phase 2: VERIFY
Read inventory.json and check if each reference exists in the skill/plugin. Updates inventory with status: exists/missing/symlink/broken.
python ./scripts/path_reference_auditor.py --project . --phase verify
Output: temp/inventory.json with status information
Phase 3: REPORT
Generate analysis reports from verified inventory (no rescanning needed).
# Summary
python ./scripts/path_reference_auditor.py --project . --phase report --report summary
# Missing files
python ./scripts/path_reference_auditor.py --project . --phase report --report missing
# Broken symlinks
python ./scripts/path_reference_auditor.py --project . --phase report --report broken_symlinks
Inventory location: All reports read from temp/inventory.json (generated by Phase 1 & 2)
What ships with it
16 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- evals/evals.json 776 B
- evals/results.tsv 301 B
- references/acceptance-criteria.md 42 B
- references/architecture.md 35 B
- references/check_plugin_boundaries.py 46 B runs code
- references/check_skill_boundaries.py 45 B runs code
- references/path_reference_auditor.py 45 B runs code
- references/usage-guide.md 34 B
- requirements.in 60 B
- requirements.txt 188 B
- scripts/build_explicit_inventory.py 44 B runs code
- scripts/check_plugin_boundaries.py 43 B runs code
- scripts/check_skill_boundaries.py 42 B runs code
- scripts/cleanup_stacked_references.py 46 B runs code
- scripts/fix_inside_plugin_symlinks.py 46 B runs code
- scripts/path_reference_auditor.py 42 B runs code
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.
- yesterday First seen · 268 lines · 96 tokens per session scan A 1584451e60cf
path-reference-auditor is a skill published in the GitHub repository richfrem/agent-plugins-skills (6 stars, last pushed yesterday), licensed MIT. It adds 96 tokens to every session and 1,938 once invoked, about $0.0005 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-03.
Other skills, from other repositories
kapso-whatsapp
How to interact with Kapso WhatsApp from the swarm — read inbound webhook payloads (text AND media), fetch message history, send free-form messages within the 24h session window (and template messages outside it), mark-as-read, show the typing indicator, send reactions, download media, verify webhook signatures, and…
composio
Use Composio from Agent Swarm through the agent-swarm x composio CLI route, the swarmx MCP tool, or a registered ctx.api.composio script connection. Trigger when a task needs connected third-party app tools such as Gmail, Google Calendar, Google Docs, Google Drive, GitHub, Slack, Notion, or HubSpot through Tool Router…
attio-interaction
Generic Attio CRM REST API v2 recipes for querying records, upserting companies/people/deals, writing notes/tasks/comments, managing lists, and handling webhooks.
swarm-scripts
Bulk, repeat, fan-out, or data-heavy work: write and run swarm scripts (inline script-run, named script-upsert, durable launch-script-run). Covers the script-vs-tool rubric, the authoring contract (args first, ctx second), the seed catalog, connections and secrets, dbquery, and exposing a script as an API.
user-management
How to manage the user registry — creating users for new Slack/GitHub/GitLab/Linear identities, managing aliases, resolving users across platforms. Use when a new human interacts with the swarm or when user identity needs updating.
scheduled-task-resilience
Guardrails for polling, scheduled jobs, and long-running external operations. Use whenever a task waits on CI, builds, deploys, browser jobs, or another asynchronous API so work survives heartbeat checks without duplicate delivery.