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 Affitor/affiliate-skills --skill templategit clone --depth 1 https://github.com/Affitor/affiliate-skillsWrote 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/affitor/affiliate-skills/template)<a href="https://agentmods.dev/skills/affitor/affiliate-skills/template"><img src="https://agentmods.dev/badge/skills/affitor/affiliate-skills/template/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/affitor/affiliate-skills/template"><img src="https://agentmods.dev/badge/skills/affitor/affiliate-skills/template.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00036 | $0.01052 |
| Opus 5.5 | $0.00014 | $0.00421 |
| Sonnet 5.5 | $0.00007 | $0.00210 |
| Haiku 4.5 | $0.00004 | $0.00105 |
Grade A, and why
your-skill-name 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- your-skill-name — 100% identical, 0 lines differ
- your-skill-name — 88% identical, 17 lines differ
How it starts
The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your Skill Name
What this skill does in 2-3 sentences. Focus on the outcome, not the process.
Stage
This skill belongs to Stage SX: StageName
When to Use
- Scenario 1
- Scenario 2
- Scenario 3
Input Schema
{
required_field: { # (required) Description
name: string # Example value
}
optional_field: string # (optional, default: "value") Description
}
Workflow
Step 1: Gather Context
What to check first. How to handle missing inputs.
Step 2: Execute Core Task
The main work the skill does.
Step 3: Format and Deliver
How to structure the output.
Output Schema
Other skills can consume these fields from conversation context:
{
primary_output: string # Main result for downstream chaining
secondary_output: string # Additional data for downstream skills
}
Output Format
## [Skill Name]: [Context]
### Section 1
[Main content]
### Section 2
[Supporting content]
Error Handling
- Missing required input: How to recover gracefully.
- External data unavailable: Fallback strategy.
- Edge case: How to handle unexpected scenarios.
Examples
Example 1: [realistic user prompt] → [step-by-step what the skill does] → [expected output summary]
Example 2: [different scenario] → [step-by-step] → [expected output summary]
Example 3: [edge case or beginner scenario] → [step-by-step] → [expected output summary]
Flywheel Connections
Feeds Into
[skill](S[X]) — [what data/output flows forward to this skill]
Fed By
[skill](S[X]) — [what data/output flows back from this skill]
Feedback Loop
- [analytics metric or data point that improves this skill's next run]
Quality Gate
Include this section for content-producing skills (S2, S3, S4, S5, S7). Remove for non-content skills.
Before delivering output, verify:
- Would I share this on MY personal social?
- Contains specific, surprising detail? (not generic)
- Respects reader's intelligence?
- Remarkable enough to share? (Purple Cow test)
- Irresistible offer framing? (if S4 offer skills ran)
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 · 164 lines · 36 tokens per session scan A 6db6e693e6aa
your-skill-name is a skill published in the GitHub repository Affitor/affiliate-skills (733 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 1,052 once invoked, about $0.0001 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-30.
Other skills, from other repositories
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
duckduckgo-search
Free keyless web, news, and image search via ddgs.
mcporter
List, auth, and call MCP servers/tools from the terminal.
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
safe-refactor
Restructure code while preserving behavior. Use for extraction, consolidation, ownership moves, or cleanup where verification must bracket structural edits.