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 TrendTweekers/article-autopilot --skill articlegit clone --depth 1 https://github.com/TrendTweekers/article-autopilotWrote 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/trendtweekers/article-autopilot/article)<a href="https://agentmods.dev/skills/trendtweekers/article-autopilot/article"><img src="https://agentmods.dev/badge/skills/trendtweekers/article-autopilot/article/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/trendtweekers/article-autopilot/article"><img src="https://agentmods.dev/badge/skills/trendtweekers/article-autopilot/article.svg" alt="Reviewed on agentmods" width="80" 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.00095 | $0.02321 |
| Opus 5.5 | $0.00038 | $0.00928 |
| Sonnet 5.5 | $0.00019 | $0.00464 |
| Haiku 4.5 | $0.00010 | $0.00232 |
Grade A, and why
article 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 1mo 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 — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
article — generalized SEO article generator
This skill composes the upstream content-brief, write-content, and
eeat-audit skills with site-specific brand context loaded from
site-config.yaml, then emits a markdown file ready to drop into your
content directory.
It is the generalized form of FakturaFlow's fakturaflow-article skill.
The pipeline shape is the value; the FakturaFlow-specific bits are
config.
Prerequisites
The upstream anthropic-skills plugin must be installed:
/plugin install anthropic-skills
If it isn't installed yet, tell the operator to run that command first, then re-invoke this skill.
Required pre-checks
Before starting, READ these files (they are the brand context and MUST be respected):
site-config.yamlat project root — brand voice, audience, terminology, output path, language profile selection..claude/skills/article/language-profiles/<profile>.md— the active language profile referenced bysite-config.yaml. Falls back toenglish.mdif unset.<output.path>/— existing articles. Don't duplicate angles. Cross-link where relevant.CLAUDE.mdat project root, if present — supplemental project conventions, do-not-do list, hard rules.
If site-config.yaml is missing, STOP and tell the operator to copy
examples/site-config.example.yaml from this repo into their project
root. Don't draft against defaults — you'll write the wrong voice.
Inputs
The operator provides ONE of:
- A target keyword — e.g.
"engineering onboarding checklist". The skill picks the angle from the SERP. - A keyword + angle — e.g.
"engineering onboarding checklist, what the first-week meeting cadence should be". - No input — read the project's keyword pool if one exists (common
paths:
.claude/seo/keywords.md,content/keywords.yaml,seo/queue.md). Pick the highest-priority unwritten keyword. Confirm with the operator before drafting.
Pipeline
What ships with it
2 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.
- 1mo ago First seen · 265 lines · 95 tokens per session scan A 84684cc08bfa
article is a skill published in the GitHub repository TrendTweekers/article-autopilot (4 stars, last pushed 5mo ago), licensed MIT. It adds 95 tokens to every session and 2,321 once invoked, about $0.0004 per session on Opus 5.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
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
projection-patterns
Build read models and projections from event streams. Use when implementing CQRS read sides, building materialized views, or optimizing query performance in event-sourced systems.
workflow-orchestration-patterns
Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.