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 byronxlg/skillfold --skill blog-postgit clone --depth 1 https://github.com/byronxlg/skillfoldWrote 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/byronxlg/skillfold/blog-post)<a href="https://agentmods.dev/skills/byronxlg/skillfold/blog-post"><img src="https://agentmods.dev/badge/skills/byronxlg/skillfold/blog-post/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/byronxlg/skillfold/blog-post"><img src="https://agentmods.dev/badge/skills/byronxlg/skillfold/blog-post.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 127 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 212 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00090 | $0.03108 |
| Opus 5 | $0.00045 | $0.01554 |
| Sonnet 5 | $0.00018 | $0.00622 |
| Haiku 4.5 | $0.00009 | $0.00311 |
Grade A, and why
blog-post 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 9d 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 — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing a blog post
The blog lives at https://byronxlg.github.io/skillfold/blog/, deployed by
.github/workflows/docs.yml on merge to main.
You write exactly one file. A post is a markdown file in
site/blog/posts/ with YAML frontmatter. scripts/build-blog.ts derives
everything else - the blog index, the post page, the RSS feed, the sitemap,
and the newest-three list on the landing page. Never hand-edit generated
output; it is gitignored and rebuilt on every deploy.
A post touches these files and no others:
| File | Change |
|---|---|
site/blog/posts/<date>-<n>-<slug>.md |
the new post (create) |
site/index.html |
only the generated block, and only via npm run build:blog |
docs/blog-todo.md |
record it under Shipped; check off a Queue item if you used one |
If you are editing site/blog/index.html, site/feed.xml,
site/sitemap.xml, or site/robots.txt, stop: those are build products.
The editorial line
This is not a product blog. A blog that explains skillfold over and over is worth nothing to anyone who has not already adopted it, and it is the default failure mode of dev-tool blogs. Do not write another one.
The blog covers the problem space skillfold lives in: agent configuration, skill distribution, reproducibility, and the supply chain underneath all of it. That space now generates real news every week. Write about the news. skillfold earns a mention when it genuinely bears on the story, and stays out of the post when it does not.
Three post types, in descending order of how often you should write them:
| Type | Tag | What it is |
|---|---|---|
| Current events | ecosystem |
A real story in the space, and what it means. The default. |
| Evergreen | concepts, feature, workflow |
A durable problem, capability, or task explained. The quiet-week fallback. |
| Rollout | release |
A large feature shipping. Only when one actually ships. |
1. Find the story
Scan the beats listed in docs/blog-todo.md for the week's strongest story.
The recurring ones:
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.
- 9d ago First seen · 269 lines · 90 tokens per session scan A 5c839d263606
blog-post is a skill published in the GitHub repository byronxlg/skillfold (12 stars, last pushed today), licensed MIT. It adds 90 tokens to every session and 3,108 once invoked, about $0.0005 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-30.
Other skills, from other repositories
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
generate-run-commands
Generate or modify run commands for the current session. Use when the user wants to set up or update run commands that appear in the session's Run button.
install-vscode-extension
How to install a VS Code extension from an extension ID. Useful when the user wants to add new capabilities to their VS Code environment by installing extensions.
get-search-view-results
Get the current search results from the Search view in VS Code.
CreateCLI
Generates production-ready TypeScript CLIs via a 3-tier template system (manual arg parsing, Commander.js, oclif), each shipping full implementation, docs, package.json, strict config, JSON output, and exit-code compliance. USE WHEN create CLI, build CLI, command-line tool, wrap API, add command, upgrade tier…
agent-browser
Browser automation for testing and verification. Use when you need to interact with web UIs, verify visual changes, fill forms, or capture screenshots.