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 fatihkan/badi --skill contentgit clone --depth 1 https://github.com/fatihkan/badiWrote 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/fatihkan/badi/content)<a href="https://agentmods.dev/skills/fatihkan/badi/content"><img src="https://agentmods.dev/badge/skills/fatihkan/badi/content.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.00055 | $0.03603 |
| Opus 5 | $0.00028 | $0.01801 |
| Sonnet 5 | $0.00011 | $0.00721 |
| Haiku 4.5 | $0.00006 | $0.00360 |
Grade A, and why
content 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 today.
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 — 555 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Production Skills
102 structured procedures
Skill List
blog-writing
The skill of creating SEO-friendly, audience-targeted blog posts. Produces value-adding blog content through research, structuring, and optimization steps.
article-writing
The long-form article writing skill with deep research and analysis. Builds source-backed articles at academic and professional standards.
technical-writing
The skill of writing technical topics clearly and in a structured way. Builds user guides, technical documents, and API documentation.
seo-content
The skill of producing search-engine-optimized content. Drives organic traffic with keyword strategy, on-page SEO, and content structuring.
landing-page-copy
The conversion-focused landing-page copy skill. Builds high-conversion pages with value propositions, social proof, and calls to action.
email-copy
The skill of writing effective copy for email campaigns. Builds high-open, high-click emails with subject lines, preheaders, body copy, and CTAs.
social-media-content
The platform-specific social content skill. Builds engagement-driven content with the right format, tone, and visual strategy per platform.
video-scripts
The skill of preparing scripts and shoot plans for video content. Builds professional scripts with story structure, scene planning, and dialogue.
podcast-planning
The podcast content planning and preparation skill. Delivers professional production with episode structure, topic selection, guest prep, and publishing strategy.
infographic-design
The skill of presenting data and information as visual infographics. Builds effective infographics with data visualization, visual hierarchy, and information flow.
ebook-creation
The digital-book planning and creation skill. Prepares professional e-books with topic research, content structuring, and design guidelines.
whitepapers
The skill of writing detailed whitepapers on technical or strategic topics. Builds research-backed, persuasive, professional B2B content.
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.
- today First seen · 555 lines · 0 tokens per session scan A de0b913ee3f0
content is a skill published in the GitHub repository fatihkan/badi (7 stars, last pushed yesterday), licensed MIT. It adds 55 tokens to every session and 3,603 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-09-06.
Other skills, from other repositories
pr-triage
4-phase PR backlog management with audit, deep code review, validated comments, and optional worktree setup. Use when triaging pull requests, catching up on pending code reviews, or managing a backlog of open PRs. Args: 'all' to review all, PR numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit…
audit-agents-skills
Audit Claude Code agents, skills, and commands for quality and production readiness. Use when evaluating skill quality, checking production readiness scores, or comparing agents against best-practice templates.
eval-agents
Audit Claude Code agents defined in .claude/agents/ for description specificity, model tier appropriateness, tools scoping, and system prompt quality. Detects dispatch ambiguity between agents, flags over-permissive tool grants, and checks for human-in-the-loop patterns that break programmatic orchestration. Use when…
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
check-cache-bugs
Audit Claude Code setup for cache bugs (CC#40524): sentinel, --resume/--continue, attribution header + ArkNill B3/B4/B5.
git-ai-archaeology
Analyze AI config evolution in a git repo. Use when mapping AI adoption history, finding when configs were first introduced, charting commit velocity by month, or identifying maturity phases in a project's AI tooling.