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 wardawgmalvicious/agent-config --skill author-skillgit clone --depth 1 https://github.com/wardawgmalvicious/agent-configWrote 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/wardawgmalvicious/agent-config/author-skill)<a href="https://agentmods.dev/skills/wardawgmalvicious/agent-config/author-skill"><img src="https://agentmods.dev/badge/skills/wardawgmalvicious/agent-config/author-skill.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.00219 | $0.04713 |
| Opus 5 | $0.00110 | $0.02357 |
| Sonnet 5 | $0.00044 | $0.00943 |
| Haiku 4.5 | $0.00022 | $0.00471 |
Grade A, and why
author-skill 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 3d 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 — 390 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Author a skill
Take a topic and end at a linted SKILL.md draft plus a runnable
fresh-session test plan. The input is a subject, not a specification —
deciding the name, the boundaries, and what the skill deliberately will
not cover is the work, not a precondition for it.
This skill is house-style. It encodes how this repo builds skills; the generic mechanics of the Agent Skills format are somebody else's job (see step 1).
Repo-relative paths below are relative to the agent-config repo
(C:\Repos\Personal\agent-config), not the session's cwd.
~/.claude/skills is a real directory holding one junction per
skill into that repo, so this skill can fire from a session in any
repo — resolve paths against agent-config regardless of where it fired.
An edit is immediate; a new skill needs the linker once. The
asymmetry follows from those per-skill junctions. Editing an
already-junctioned skill is live the moment it hits disk, for every
session on this machine, committed or not. But a directory that did not
exist at the last scripts/link-claude.ps1 run has no junction, so
a newly authored skill is invisible everywhere — absent from the
listing, and /<name> answers Unknown command. Measured 2026-09-02:
land was missing from a listing of 8 junctions immediately after its
SKILL.md was written, and appeared only once the linker ran. On this
machine the form is ./scripts/link-claude.ps1 -SkillGroups workflow,
never bare — see root CLAUDE.md.
A platform skill is the exception that proves the rule: fabric and
powerbi are pruned from user scope here on purpose, so a new one stays
unlinked by design and enters no session's payload. Nothing is broken
when that happens, and no linker run changes it.
Once linked, a half-drafted skill is a live half-drafted skill; finish the frontmatter before walking away.
1. Check this is the right skill
Two routes out, both cheap to check first.
Guidance that already exists → /learn. The dividing line is whether
the destination exists. /learn folds a session learning into a skill,
rule, or CLAUDE.md that should already have covered it. This skill
creates guidance that has no home yet. A learning that arrives as "the
fabric-cicd skill was wrong about X" is /learn work even if the fix
is large.
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.
- 3d ago Changed · +13 lines 065cfa55e6d1
- 4d ago Changed · +65 lines · +17 tokens per session 5102ebdfb22b
- 8d ago First seen · 312 lines · 202 tokens per session scan A 81b258922629
author-skill is a skill published in the GitHub repository wardawgmalvicious/agent-config (1 stars, last pushed today), licensed MIT. It adds 219 tokens to every session and 4,713 once invoked, about $0.0011 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-31.
Other skills, from other repositories
marketing-strategy-pmm
Product marketing, positioning, GTM strategy, and competitive intelligence. Includes ICP definition, April Dunford positioning methodology, launch playbooks, competitive battlecards, and international market entry guides. Use when developing positioning, planning product launches, creating messaging, analyzing…
loki-mode
Multi-agent autonomous startup system for Claude Code. Triggers on "Loki Mode". Orchestrates 100+ specialized agents across engineering, QA, DevOps, security, data/ML, business operations, marketing, HR, and customer success. Takes PRD to fully deployed, revenue-generating product with zero human intervention.…
email-sequence
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," or "lifecycle…
qa-test-planner
Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.
gepetto
Creates detailed, sectionized implementation plans through research, stakeholder interviews, and multi-LLM review. Use when planning features that need thorough pre-implementation analysis.
content-research-writer
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.