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 petar-djukic/writing-skills --skill match-structuregit clone --depth 1 https://github.com/petar-djukic/writing-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/petar-djukic/writing-skills/match-structure)<a href="https://agentmods.dev/skills/petar-djukic/writing-skills/match-structure"><img src="https://agentmods.dev/badge/skills/petar-djukic/writing-skills/match-structure/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/petar-djukic/writing-skills/match-structure"><img src="https://agentmods.dev/badge/skills/petar-djukic/writing-skills/match-structure.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.00146 | $0.01838 |
| Opus 5 | $0.00073 | $0.00919 |
| Sonnet 5 | $0.00029 | $0.00368 |
| Haiku 4.5 | $0.00015 | $0.00184 |
Grade A, and why
match-structure 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 11d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Split from the original match-structure (GH-291, 2026-07): the
section-level driver (compare, blueprint extraction, section-by-section
rewrite) moved to match-outline. This skill retains the quantitative
metrics engine, corpus aggregation, frequency analysis, and the similarity
guard that other prose skills import.
Match structure (paragraph/sentence-level metrics)
This skill provides the quantitative style measurement layer that other
prose skills depend on. It profiles markdown papers at the sentence and
paragraph level — distributions, passive voice, hedging, citation density,
word and phrase frequencies, stock idiom usage — and aggregates those into
a corpus profile. It also provides the similarity plagiarism guard used by
match-outline's rewrite mode and match-voice's verify step.
Where things live
- Corpus:
<db-dir>/papers/*.md— the markdown conversions fetched byupdate-references, selected via entries inreferences.yaml. Default selection is entries withstatus: summarized; pass--alltostyle.py corpusto include every entry with anmd_path. - Quantitative profile:
<db-dir>/voice-profile.json, written bystyle.py corpus. Regenerate only when the corpus changes. - Voice anchors: passage-level tf-idf retrieval from
writing-voice/exemplars, viavoice_anchors.py. - Venue profiles:
writing-voice/venues/<name>.yaml— per-venue parameter bundles (anchor query, blueprint, targets, tell lexicon, gates) consumed by humanize/filter-tells/tighten-style. Schema in thewriting-voicerepository rule; loader/validator isvenue_profile.py.
Running the scripts
RUN="pixi run --manifest-path <skill>/../../pixi.toml python"
style.py subcommands
$RUN <skill>/scripts/style.py --db <db-path> profile <paper.md> # one paper, full JSON
$RUN <skill>/scripts/style.py --db <db-path> corpus # aggregate, write voice-profile.json
$RUN <skill>/scripts/style.py --db <db-path> compare <draft.md> # metric deltas vs corpus
$RUN <skill>/scripts/style.py freq <paper.md> # frequency tables only
$RUN <skill>/scripts/style.py similarity <file> --against <sources> [--baseline <draft>]
$RUN <skill>/scripts/style.py burstiness <draft.md> [--baseline <before.md>] [--per-paragraph] [--text]
What ships with it
11 files 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.
- scripts/match_structure.py 683 B runs code
- scripts/style.py 38 KB runs code
- scripts/testdata/test_diction_weight.py 8.8 KB runs code
- scripts/testdata/test_style_frontmatter.py 5.0 KB runs code
- scripts/testdata/test_style_metrics.py 14 KB runs code
- scripts/testdata/test_style_yaml.py 2.0 KB runs code
- scripts/testdata/test_venue_profile.py 6.4 KB runs code
- scripts/testdata/test_voice_anchors.py 13 KB runs code
- scripts/testdata/test_voice_corpus.py 4.7 KB runs code
- scripts/venue_profile.py 19 KB runs code
- scripts/voice_anchors.py 18 KB runs code
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.
- 11d ago First seen · 149 lines · 146 tokens per session scan A 257a47899dde
match-structure is a skill published in the GitHub repository petar-djukic/writing-skills (4 stars, last pushed 7d ago), licensed MIT. It adds 146 tokens to every session and 1,838 once invoked, about $0.0007 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
humanizer
Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague…
structural-humanizer
Remove the discourse-level (structural) signs of AI writing that survive surface editing: stated lessons and moral-of-the-story closers, tidy single-track arcs, embodied-emotion performance ("chest tightened"), vague allusions instead of named references, unbroken linear structure, and shape convergence across pieces.…
story-import
A tool for turning an existing novel into a structured writing project. It analyzes the book and organizes its characters, settings, plot plans, chapters, and tracking data for later writing.
story-review
A review workflow for finding story problems from several viewpoints, including issues with structure, characters, wording, and fictional world rules. It can use multiple reviewer agents or work alone.
story-long-analyze
A long-form fiction analysis workflow for breaking down a novel’s opening chapters, characters, pacing, turning points, relationships, and overall structure.
story-deslop
A writing editor for Chinese web novels that detects writing patterns often associated with AI-generated text and makes the prose feel more natural.