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 structure-checkergit 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/structure-checker)<a href="https://agentmods.dev/skills/ur-grue/autopunk-media-skills/structure-checker"><img src="https://agentmods.dev/badge/skills/ur-grue/autopunk-media-skills/structure-checker/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/structure-checker"><img src="https://agentmods.dev/badge/skills/ur-grue/autopunk-media-skills/structure-checker.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.00041 | $0.02028 |
| Opus 5 | $0.00020 | $0.01014 |
| Sonnet 5 | $0.00008 | $0.00406 |
| Haiku 4.5 | $0.00004 | $0.00203 |
Grade A, and why
structure-checker 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 7d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Structure Checker
What This Skill Does
Analyses a draft article's structural architecture — paragraph order, logical flow, redundancies, and pacing — and returns a diagnostic report with specific reordering, cutting, or restructuring recommendations.
When To Use This Skill
- A draft feels "off" but you cannot pinpoint why — it may be a structural problem rather than a prose problem
- An article has been through multiple revisions and the original architecture has drifted
- You are editing a long-form piece (2,000+ words) and want to verify the structural logic before line-editing
- A writer has submitted a draft where the information is solid but the organisation is unclear
What You Need To Provide
Required: The full draft text.
Optional: The intended article type (news report, feature, investigative, opinion, profile, explainer) — this affects what structural conventions the assistant evaluates against; specific concerns (e.g., "the middle section feels slow," "I'm not sure the ending works"); the target publication or audience, if relevant to structure expectations.
How the Assistant Approaches This
-
Maps the architecture. Reads the full draft and creates a paragraph-by-paragraph outline: what each paragraph does (introduces, provides evidence, quotes a source, transitions, contextualises, concludes). This map reveals the skeleton of the piece without the distraction of prose quality.
-
Evaluates against structural conventions. Checks the draft against the conventions for its article type. For news: inverted pyramid, most important information first, attribution high. For features: narrative arc, scene-setting, tension and resolution. For investigative: evidence-claim-evidence structure, source diversity, clear separation of fact and analysis. For opinion: thesis stated early, evidence marshalled logically, counterarguments addressed, strong close.
-
Flags structural problems. Identifies specific issues: paragraphs that are out of logical order; redundant passages that make the same point twice; sections where the energy drops (typically where context or background is front-loaded instead of distributed); missing transitions that leave the reader stranded between ideas; endings that arrive too suddenly or trail off.
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.
- 7d ago First seen · 119 lines · 41 tokens per session scan A f8aded195072
structure-checker is a skill published in the GitHub repository ur-grue/autopunk-media-skills (30 stars, last pushed 11d ago), licensed MIT. It adds 41 tokens to every session and 2,028 once invoked, about $0.0002 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-09-04.
Other skills, from other repositories
code-architecture
Application architecture patterns and code organization — clean architecture, hexagonal architecture, feature-based structure, dependency inversion, module boundaries, SOLID principles at module scale. Activate on "clean architecture", "hexagonal architecture", "feature-based structure", "dependency inversion"…
architecture-patterns
Architecture validation and patterns for clean architecture, backend structure enforcement, project structure validation, test standards, and context-aware sizing. Use when designing system boundaries, enforcing layered architecture, validating project structure, defining test standards, or choosing the right…
compression
Cuts a draft to a target word count without losing substance. Two modes behind one skill. target-count hits a specific number (200 for a cold email, 500 for an op-ed, 6 for a product summary). redundancy catches the specific failure where a phrase says what the verb or context already implied — "going forward" after a…
vividness
Pushes a draft from abstract toward concrete at two scales. Noun-level (replaces "dog" with "German shepherd," "customer" with "Sarah at JPMorgan's options-trading desk," "many" with "47 of 100") and scene-level (turns "I was angry" into the body signal, room, and dialogue). Implements Kramon's "specific over…
dealing-with-reporters
Drafts and reviews answers to reporter questions, on-the-record statements, crisis-comms responses, and press-inquiry replies. Implements Andrew Ross Sorkin's 11 rules (taught with Kramon at Stanford GSB) plus AP attribution definitions for off-the-record / background / deep background conversations. Use when a…
sent-mail-outcome-tracker
Read the user's recent cold-outreach sent mail, look up which messages got replies, classify reply sentiment, and produce an outcome report that surfaces what the responders had in common. Use when the user says "did my cold emails get replies," "what's my reply rate," "sent-mail outcomes," "track outcomes," or…