Borrowing it
Nothing to install: this file belongs to ShawnBaek/kindle-weekly-letter. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ShawnBaek/kindle-weekly-letter/main/.claude/skills/add-topic/SKILL.mdgit clone --depth 1 https://github.com/ShawnBaek/kindle-weekly-letterWrote 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/shawnbaek/kindle-weekly-letter/add-topic)<a href="https://agentmods.dev/skills/shawnbaek/kindle-weekly-letter/add-topic"><img src="https://agentmods.dev/badge/skills/shawnbaek/kindle-weekly-letter/add-topic/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/shawnbaek/kindle-weekly-letter/add-topic"><img src="https://agentmods.dev/badge/skills/shawnbaek/kindle-weekly-letter/add-topic.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.00025 | $0.00492 |
| Opus 5 | $0.00013 | $0.00246 |
| Sonnet 5 | $0.00005 | $0.00098 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
add-topic 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 12d 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.
What it actually says
Add Topic to Kindle Weekly Letter
The user wants to add a new topic: $ARGUMENTS
Follow these steps:
Step 1: Gather Details
Ask the user:
- Topic name — What should this topic be called in the EPUB?
- Audience — Who is this for? (e.g., "senior engineers", "product managers", "beginners")
- Focus areas — What subtopics should the agent search for? (list 3-5)
- Preferred sources — Any specific websites, blogs, or publications to prioritize?
- What to avoid — Any sources or content types to skip?
Step 2: Create Agent Prompt
Create a new file at prompts/agent_{topic_id}.md following the same format as existing agent prompts in the prompts/ directory. Read one (e.g., prompts/agent_ai_news.md) as a reference template.
The agent prompt must:
- Describe the research task clearly
- List preferred sources
- Specify quality criteria
- Return the standard JSON structure with: topic, articles, section_intro
Step 3: Add Sources Config
Add an entry to sources.json for the new topic with the user's preferred sources. Read the existing sources.json to understand the format.
Step 4: Register Topic
Add the new topic to src/config.py in the TOPICS list:
{
"id": "{topic_id}",
"name": "{Topic Name}",
"prompt_file": "agent_{topic_id}.md",
},
Step 5: Update Prompts
Add the new agent to:
prompts/daily_collector.md— add to the agent prompts listprompts/sunday_compiler.md— add to the proposal display template
Step 6: Confirm
Tell the user:
- Topic "{Topic Name}" has been added
- It will start collecting articles at the next daily run
- They can run
/collect-nowto start immediately - They can edit sources in
sources.json
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.
- 12d ago First seen · 61 lines · 25 tokens per session scan A c14461946c8b
add-topic is a skill published in the GitHub repository ShawnBaek/kindle-weekly-letter (2 stars, last pushed 5mo ago), licensed MIT. It adds 25 tokens to every session and 492 once invoked, about $0.0001 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
hive.chart-creation-foundations
Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
shogun-screenshot
A screenshot tool for getting images from a computer or web page and then cropping, resizing, or masking sensitive information. Playwright is a browser-automation tool used here to capture web pages.
agent-qa-testing
Agent davranis testi ve protokol uyumluluk dogrulamasi. Agent'larin tanimli rollerine uygun davranip davranmadigini assertion-based test'lerle olcer. Personality drift, role violation ve output kalite regresyonu tespit eder.
aws-patterns
Lambda best practices, S3 event patterns, SQS/SNS fanout, and DynamoDB access patterns for serverless AWS architectures.
review
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use…