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 gpsaggese/helpers --skill blog.create_tilgit clone --depth 1 https://github.com/gpsaggese/helpersWrote 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/gpsaggese/helpers/blog.create_til)<a href="https://agentmods.dev/skills/gpsaggese/helpers/blog.create_til"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/blog.create_til/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/gpsaggese/helpers/blog.create_til"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/blog.create_til.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.00008 | $0.00425 |
| Opus 5.5 | $0.00003 | $0.00170 |
| Sonnet 5.5 | $0.00002 | $0.00085 |
| Haiku 4.5 | $0.00001 | $0.00042 |
Grade A, and why
blog.create_til 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 yesterday.
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
Goal
- Write a concise, engaging "Today I Learned" (TIL) blog post on the user's topic
Workflow
Structure
- Title
- What I Learned
- Why It Matters
- Example / Demonstration
- Key Takeaways
- References or Further Reading
- The post should:
- Start with a short intro: what I learned and why it caught my attention
- Explain the concept in simple language for engineers and curious readers
- Include a practical example, code snippet, or real-world use case if relevant
- Highlight surprising insights, common misconceptions, or lessons learned
- End with key takeaways and actionable advice for further exploration
Use Front Matter and TL;DR
- Add front matter as in
.claude/skills/blog.rules.md## Front Matter (YAML) - Add TL;DR as in
.claude/skills/blog.rules.md## TL;DR Section
Beautify
- Run a command to format the code for proper visualization
> prettier --tab-width 4 --prose-wrap always --print-width 80 -w <FILE>
Conventions
Tone
- Conversational and reflective
- Technical but accessible
- Curious and educational
Length
- Keep the post between 500 and 1000 words. Favor clarity and practical value over exhaustive coverage
Formatting Rules
-
Write using bullet points
-
Follow the rules in:
.claude/skills/blog.rules.md.claude/skills/markdown.rules.md.claude/skills/text.rules.md
Verification
- Confirm front matter and a TL;DR are present per
.claude/skills/blog.rules.md - Confirm the post is between 500 and 1000 words
- Confirm
prettierran without errors
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.
- yesterday First seen · 69 lines · 8 tokens per session scan A f1407f6e7912
blog.create_til is a skill published in the GitHub repository gpsaggese/helpers (158 stars, last pushed today), licensed Apache-2.0. It adds 8 tokens to every session and 425 once invoked, about $0.0000 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-11-06.
blog.create_til compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| blog.create_tilgpsaggese/helpers | Skill | 158 | today | Apache-2.0 | A | 8 | Claude Code |
| hr-onboardingnexu-io/open-design | Skill | 106k | today | Apache-2.0 | A | 62 | Claude Code, Codex |
| book-mirrorgarrytan/gbrain | Skill | 32k | today | MIT | A | 138 | Claude Code |
| exam-forecastanthropics/claude-for-legal | Skill | 9.9k | today | Apache-2.0 | A | 73 | Claude Code |
| lean-formalizewanshuiyin/Auto-claude-code-research-in-sleep | Skill | 19k | yesterday | MIT | A | 81 | Claude Code |
| deck-course-modulenexu-io/html-anything | Skill | 9.4k | yesterday | Apache-2.0 | A | 25 | Claude Code, Codex |
| eli5companion-inc/feynman | Skill | 10k | 7d ago | MIT | A | 63 | Claude Code, Codex |