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 ur-grue/autopunk-media-skills --skill cms-fields-writergit clone --depth 1 https://github.com/ur-grue/autopunk-media-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/ur-grue/autopunk-media-skills/cms-fields-writer)<a href="https://agentmods.dev/skills/ur-grue/autopunk-media-skills/cms-fields-writer"><img src="https://agentmods.dev/badge/skills/ur-grue/autopunk-media-skills/cms-fields-writer/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/ur-grue/autopunk-media-skills/cms-fields-writer"><img src="https://agentmods.dev/badge/skills/ur-grue/autopunk-media-skills/cms-fields-writer.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.00047 | $0.01225 |
| Opus 5.5 | $0.00019 | $0.00490 |
| Sonnet 5.5 | $0.00009 | $0.00245 |
| Haiku 4.5 | $0.00005 | $0.00122 |
Grade A, and why
cms-fields-writer 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 2mo 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CMS Fields Writer
What This Skill Does
Generates the complete set of metadata fields — tags, categories, keywords, slug, and summary — needed to publish a piece of content in a content management system, ready to copy and paste into each field.
When To Use This Skill
- You have finished writing or editing a piece and need to fill in all the CMS fields before publishing
- A sub-editor or social media manager needs to hand off a complete metadata package with the article
- You are republishing or updating archived content and need to refresh its metadata to current house style
- You are onboarding a new contributor and want to show them a standard metadata set for a typical article
What You Need To Provide
Required:
- The article or content text (paste the full text, or a detailed summary if the piece is very long)
- Publication name or type (e.g. "daily news site", "monthly trade magazine", "broadcast news service")
Optional:
- Your tag taxonomy or category list — paste your site's existing categories so the assistant matches them exactly rather than inventing new ones
- Maximum number of tags permitted by your CMS
- Preferred slug format (e.g. lowercase-hyphenated, date-prefixed)
- Whether a meta description is needed in addition to the on-page summary
- Audience or section (e.g. "Politics section", "consumer-facing")
How the Assistant Approaches This
- Reads the content and identifies the primary topic, secondary topics, named entities (people, places, organisations, events), and content format (news, feature, opinion, explainer).
- Maps these to the metadata fields typically required by a CMS: title tag, slug, category, primary tags, secondary tags, keywords, and summary or standfirst. If a category list was provided, it matches categories to that list exactly.
- Presents each field on its own clearly labelled line so you can copy individual values directly into each CMS input field without reformatting.
Output Format
A labelled list, one field per line, with no additional commentary. Each label is followed by a colon and the value. Tags and keywords are comma-separated on a single line. The summary is a single sentence of 25–35 words in active voice. The slug is lowercase and hyphenated. Example structure:
What ships with it
1 file 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.
- 2mo ago First seen · 89 lines · 47 tokens per session scan A 9d10b4634880
cms-fields-writer is a skill published in the GitHub repository ur-grue/autopunk-media-skills (38 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 1,225 once invoked, about $0.0002 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
build-ghost-app-ui
Build a Ghost app's screens with Shade, Ghost's design system, and find its docs and skills. Use when building or changing a Ghost app's UI, or adding Shade to an app.
ghost-app-ui-dev-setup
Prepare an empty folder for trying Ghost app UI development locally, with Shade's skills, local docs and the app SDK from a Ghost checkout.
shade-page-templates
Start a Ghost screen from the Shade page template for its page type. Use when starting a new page, route or screen, or when restructuring a page's chrome.
shade-tokens-not-hex
Colour Ghost UI with Shade's semantic tokens. Use when choosing colours or styling UI, including surfaces, text, borders and hover states.
shade-page-header
Build or revise a page header with Shade's PageHeader contract. Use when adding a page header, changing its actions, or reviewing action order, search, filtering, dropdowns, tooltips or responsive behaviour in a header.
shade-imports
Import Shade from its layer subpaths and set up its stylesheet and ShadeApp for the surface. Use when importing from @tryghost/shade or adding Shade to an app.