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/odradekai/bundles-forge/auditingnpx skills add OdradekAI/bundles-forge --skill auditinggit clone --depth 1 https://github.com/OdradekAI/bundles-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/odradekai/bundles-forge/auditing)<a href="https://agentmods.dev/skills/odradekai/bundles-forge/auditing"><img src="https://agentmods.dev/badge/skills/odradekai/bundles-forge/auditing.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.00050 | $0.04936 |
| Opus 5 | $0.00025 | $0.02468 |
| Sonnet 5 | $0.00010 | $0.00987 |
| Haiku 4.5 | $0.00005 | $0.00494 |
Grade A, and why
auditing 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 — 349 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auditing Bundle-Plugins
Overview
Systematically evaluate a bundle-plugin project or a single skill across applicable quality categories — including security scanning — score each, and produce a diagnostic report. This skill is a pure diagnostic tool: it identifies and reports issues but does not orchestrate fixes.
Core principle: Measure and report. A scored audit gives orchestrating skills (blueprinting, optimizing, releasing) the information they need to decide what to fix. When sources contradict, apply the authority hierarchy in references/source-of-truth-policy.md.
This skill includes security scanning. No need to invoke a separate security skill — see Category 10 under Full Project Audit.
Announce at start: "I'm using the auditing skill to audit [this project / this skill]."
Plugin context: When installed as a plugin, operate on the user's project ($CLAUDE_PROJECT_DIR / <target-dir>), not the plugin's own cache. Read files from and detect scope in the target; write all outputs (reports, JSON baselines) to the workspace's .bundles-forge/audits/. See references/input-normalization.md for edge-case input types, naming conventions, and security rules. <plugin-root> in commands below resolves to $CLAUDE_PLUGIN_ROOT (Claude Code), $CURSOR_PLUGIN_ROOT (Cursor), or . (local development).
Resolve Input & Detect Scope
The target can be a local path, a GitHub URL, or a zip file. Normalize to a local directory, then detect scope. This applies to all three audit modes.
Input Normalization
This is a mandatory step — do not skip it or improvise paths. Resolve the target to a local directory before proceeding to Scope Detection or any audit Step 1.
- Resolve the workspace. The workspace is
$CLAUDE_PROJECT_DIRor$CURSOR_PROJECT_DIR(plugin mode), falling back to the current working directory. - Normalize the target by type:
- Local path — use directly; no transformation needed.
- GitHub URL — parse
<owner>and<repo>from the URL. Shallow-clone to<workspace>/.bundles-forge/repos/<owner>__<repo>/using--depth 1 --no-checkout, then rungit checkout. If the directory already exists, append a__<YYYYMMDD>timestamp to avoid collisions. Do not clone to/tmp/,~/, or any path outside.bundles-forge/repos/. - Zip/tar.gz — extract to
<workspace>/.bundles-forge/repos/<archive-name>/.
- Create the target subdirectory if it does not exist.
- On failure (network error, 404, auth required, rate limit): tell the user what failed and suggest providing a local path or zip file instead. Do not silently skip or proceed with partial data.
What ships with it
21 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.
- references/audit-checks.json 40 KB
- references/input-normalization.md 1.9 KB
- references/plugin-checklist.md 15 KB
- references/plugin-report-template.md 8.8 KB
- references/report-examples.md 4.4 KB
- references/security-checklist.md 16 KB
- references/skill-checklist.md 6.4 KB
- references/skill-report-template.md 7.2 KB
- references/source-of-truth-policy.md 6.4 KB
- references/workflow-checklist.md 6.1 KB
- references/workflow-report-template.md 6.6 KB
- scripts/_cli.py 2.2 KB runs code
- scripts/_graph.py 11 KB runs code
- scripts/_parsing.py 6.8 KB runs code
- scripts/_scoring.py 1.7 KB runs code
- scripts/audit_docs.py 32 KB runs code
- scripts/audit_plugin.py 19 KB runs code
- scripts/audit_security.py 23 KB runs code
- scripts/audit_skill.py 33 KB runs code
- scripts/audit_workflow.py 15 KB runs code
- scripts/generate_checklists.py 11 KB 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.
- 5d ago First seen · 349 lines · 50 tokens per session scan A a7ec487ec2cc
auditing is a skill published in the GitHub repository OdradekAI/bundles-forge (230 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 50 tokens to every session and 4,936 once invoked, about $0.0003 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
integrate-arcjet-guard-claude-agent-sdk-py
Integrate Arcjet Guard into the Python Claude Agent SDK — wrap authored @tool with guardtool, and use guardhooks for UserPromptSubmit inbound plus PreToolUse on unwrapped built-ins / MCP. Use when asked to add Arcjet to claude-agent-sdk, rate limit those tools, screen inbound prompts, or block prompt injection / PII.…
integrate-arcjet-guard-claude-managed-agents-py
Integrate Arcjet Guard into Python Claude Managed Agents — screen user.message with guardevents before sessions.events.send, and gate custom tools on agent.customtooluse with guardcustomtool. Use when asked to add Arcjet to hosted Claude Managed Agents, anthropic beta sessions, rate limit custom tools, or block prompt…
integrate-arcjet-guard-crewai
Integrate Arcjet Guard into official CrewAI — register process-wide PRETOOLCALL with registerarcjethooks, or wrap a standalone BaseTool you call yourself with guardtool. Use when asked to add Arcjet to CrewAI, LiteAgent, crew-injected tools, rate limit those tools, screen inbound messages before kickoff, or block…
integrate-arcjet-guard-langchain-py
Integrate Arcjet Guard into Python LangChain — wrap a BaseTool you call with guardtool, put ArcjetMiddleware + ToolPolicy on createagent, or observe a chain with ArcjetCaptureHandler. Use when asked to add Arcjet to LangChain, createagent, langchain-core tools, rate limit those tools, screen inbound messages, or block…
integrate-arcjet-guard-strands-agents-py
Integrate Arcjet Guard into Python Strands Agents — wrap authored @tool with guardtool, and put guardhooks on Agent(hooks=) for unwrapped / MCP tools via BeforeToolCallEvent.canceltool. Use when asked to add Arcjet to strands / strands-agents, rate limit those tools, screen inbound messages, or block prompt injection…
integrate-arcjet-guard-openai-agents-py
Integrate Arcjet Guard into Python OpenAI Agents — wrap FunctionTool / functiontool with guardtool and read a caller-owned session or conversation id via openaiagentscontext. Use when asked to add Arcjet to openai-agents, Runner.run, rate limit those tools, screen inbound messages, or block prompt injection / PII.…