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 realjaymes/marketingagentskills --skill agent-skill-buildergit clone --depth 1 https://github.com/realjaymes/marketingagentskillsWrote 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/realjaymes/marketingagentskills/agent-skill-builder)<a href="https://agentmods.dev/skills/realjaymes/marketingagentskills/agent-skill-builder"><img src="https://agentmods.dev/badge/skills/realjaymes/marketingagentskills/agent-skill-builder.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.00096 | $0.01836 |
| Opus 5 | $0.00048 | $0.00918 |
| Sonnet 5 | $0.00019 | $0.00367 |
| Haiku 4.5 | $0.00010 | $0.00184 |
Grade A, and why
agent-skill-builder 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 7d 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Skill Builder
Quickly scaffolds new Claude Code skills or translates ChatGPT projects into Claude Code format. This skill focuses on fast creation and correct structure. For iterative testing, benchmarking, and description optimization, use /skill-creator.
Two Modes
Mode 1: Create New Skill (/agent-skill-builder new [name])
Scaffolds a fresh Claude Code skill with proper structure and best practices.
Mode 2: Translate ChatGPT Project (/agent-skill-builder translate [name])
Converts an existing ChatGPT project into a Claude Code skill.
Create New Skill
Step 1: Gather Intent
Ask the user (skip what's already clear from context):
- Skill name: What should the
/slash-commandbe called? - Purpose: What does this skill do?
- Examples: How would this skill be used in practice?
- Triggers: What would a user say that should invoke this skill?
Step 2: Plan Resources
Analyze each example to identify what should be bundled:
- Scripts (
scripts/): Code rewritten repeatedly or needing deterministic reliability. Execute without loading into context. - References (
references/): Documentation Claude should consult while working. Loaded on demand. - Assets (
assets/): Files used in output (templates, images, fonts). Not loaded into context.
Step 3: Create Directory and SKILL.md
mkdir -p ~/.claude/skills/[skill-name]
Write SKILL.md following this template:
---
name: skill-name
description: "Describes what the skill does and specific triggers for when to use it. Write in third person. Include keywords users would say. Max 1024 characters. This is the PRIMARY triggering mechanism."
---
# Skill Name
[1-2 sentence description]
## Instructions
[Step-by-step guidance — use imperative form]
## Output Format
[Expected output structure]
## Constraints
[Limitations and rules]
Step 4: Add Reference Files (if needed)
For skills with multiple domains or variants, keep SKILL.md lean and split into references:
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.
- 7d ago First seen · 195 lines · 96 tokens per session scan A a4ba5627c30a
agent-skill-builder is a skill published in the GitHub repository realjaymes/marketingagentskills (56 stars, last pushed 10d ago), licensed MIT. It adds 96 tokens to every session and 1,836 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…