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/authoringnpx skills add OdradekAI/bundles-forge --skill authoringgit 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/authoring)<a href="https://agentmods.dev/skills/odradekai/bundles-forge/authoring"><img src="https://agentmods.dev/badge/skills/odradekai/bundles-forge/authoring.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.1 | $0.00043 | $0.02628 |
| Opus 5 | $0.00022 | $0.01314 |
| Sonnet 5 | $0.00009 | $0.00526 |
| Haiku 4.5 | $0.00004 | $0.00263 |
Grade A, and why
authoring 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authoring Skill Content
Overview
Guide the authoring of effective SKILL.md files, agent definitions (agents/*.md), and supporting resources within a bundle-plugin. Good content is the difference between skills that agents consistently find and follow — and ones that get ignored or misinterpreted.
Core principle: Write for the agent's experience. Every instruction should be discoverable (good description), loadable (right size), and followable (clear, motivated instructions). Skills are the first-class source of truth in a bundle-plugin — docs and README must not contradict skill content (see bundles-forge:auditing — references/source-of-truth-policy.md).
Skill type: Hybrid — follow the execution flow rigidly (Entry Detection → Path steps → Validation), but apply writing guidance flexibly based on context. The process is discipline-enforcing; the content decisions are pattern-based.
Announce at start: "I'm using the authoring skill to help [write / complete / improve / adapt] [skill / agent] content."
Entry Detection
Determine the authoring path from context:
| Context | Path |
|---|---|
skill-inventory from blueprinting, or user requests writing new SKILL.md / agent definition from scratch |
Path 1: New Content |
| User provides an existing/external skill to add into a project, or asks to adapt a skill to match project conventions | Path 2: Integrate Content |
scaffold-output directories exist but SKILL.md body has < 10 non-empty lines |
Path 3: Complete Content |
User provides existing in-project skill-md to improve, or optimization-spec from optimizing with specific changes |
Path 4: Improve Content |
When the target is an agent definition (agents/*.md) rather than a skill, follow the same path logic but use the agent authoring conventions from references/agent-authoring-guide.md.
Step 0: Project Context (all paths)
Before writing any content, verify scope and detect the project context:
What ships with it
3 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.
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 · 157 lines · 43 tokens per session scan A bad88f588580
authoring is a skill published in the GitHub repository OdradekAI/bundles-forge (230 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 43 tokens to every session and 2,628 once invoked, about $0.0002 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
add-ai-protection
Deprecated: use the arcjet skill instead. Adds security protection to AI/LLM endpoints and non-HTTP code paths — prompt injection detection, PII blocking, and token budget rate limiting.
add-guard-protection
Deprecated: use the arcjet skill instead. Adds Arcjet Guard protection to AI agent tool calls, background jobs, queue workers, and other non-HTTP code paths.
add-request-protection
Deprecated: use the arcjet skill instead. Adds security protection to a server-side route or endpoint — rate limiting, bot detection, email validation, and abuse prevention.
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.…
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-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…