Borrowing it
Nothing to install: this file belongs to donaldrichard19-LVD/pattern-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/donaldrichard19-LVD/pattern-mcp/main/.claude/skills/pattern-docs-sync/SKILL.mdgit clone --depth 1 https://github.com/donaldrichard19-LVD/pattern-mcpWrote 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/donaldrichard19-lvd/pattern-mcp/pattern-docs-sync)<a href="https://agentmods.dev/skills/donaldrichard19-lvd/pattern-mcp/pattern-docs-sync"><img src="https://agentmods.dev/badge/skills/donaldrichard19-lvd/pattern-mcp/pattern-docs-sync/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/donaldrichard19-lvd/pattern-mcp/pattern-docs-sync"><img src="https://agentmods.dev/badge/skills/donaldrichard19-lvd/pattern-mcp/pattern-docs-sync.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.00076 | $0.01183 |
| Opus 5.5 | $0.00030 | $0.00473 |
| Sonnet 5.5 | $0.00015 | $0.00237 |
| Haiku 4.5 | $0.00008 | $0.00118 |
Grade A, and why
pattern-docs-sync 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 1mo 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pattern docs sync
Pattern keeps two published Artifacts that are supposed to track the repo,
not drift from it. This skill is the checklist for keeping them honest.
Both are owned by this user — update them in place via the Artifact tool's
url param. Never publish a new artifact for either; that creates a second,
disconnected URL.
- Pattern Briefing — PM-facing positioning/architecture/risk brief.
https://claude.ai/code/artifact/a87c4898-fa0f-4748-bc29-978ab9dd57be - Pattern Primer — engineering-facing doc explaining the reasoning
behind Pattern's architecture: eight design principles, each tied to a
real decision or finding, plus decision-rights and a glossary.
https://claude.ai/code/artifact/2d064e6d-53d5-4a8f-9965-303364fd6985
Always Artifact action: "read" with the url first — republishing
without reading the live version risks clobbering a change made outside
this session, and the tool will refuse a stale publish anyway. Edit the
saved local HTML file, then Artifact action: "publish" with file_path
set to that same file and url set to the artifact's URL.
Rule 1 — new BACKLOG.md item → Pattern Briefing
Trigger: a new ## section is added to BACKLOG.md (a new feature idea,
not a routine edit to an existing section).
- Read the Pattern Briefing artifact.
- Find the
Opportunitiessection (<div class="ranked">of.ranked-item.opportunityblocks, each<span class="rank-mark">NN</span><h4>+<p>). Append a new entry at the next rank number.
- If the item is a genuine risk/concern rather than an upside, use the
.ranked-item.riskvariant instead if the section supports it — check how existing risk entries are marked in theRiskssection and match that shape rather than forcing everything intoOpportunities. - If it's better framed as an unresolved question than a proposed
direction (e.g. something explicitly parked pending user demand),
add it to
Open questions to closeinstead — a plain<li>.
- Write the entry in the doc's own voice: plain business prose, no function/variable names, no raw markdown from BACKLOG.md pasted in. Translate "why this matters" into product/cost/quality terms a non-engineer reader would follow — see existing entries for the register (e.g. "Build a dedicated connection to each source — the long-term moat"). Carry over the backlog item's actual effort/priority framing (parked vs. active vs. sequenced) rather than implying it's imminent work if it isn't.
- Publish back to the same URL. Don't touch unrelated sections.
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.
- 1mo ago First seen · 88 lines · 76 tokens per session scan A bb20ea85da6d
pattern-docs-sync is a skill published in the GitHub repository donaldrichard19-LVD/pattern-mcp (9 stars, last pushed yesterday), licensed MIT. It adds 76 tokens to every session and 1,183 once invoked, about $0.0003 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-09-04.
Other skills, from other repositories
kami-landing
Produce a print-grade single-page kami (紙 / 纸) document — warm parchment canvas, ink-blue accent, serif at one weight, no italic, no cool grays. The output reads like a professional white paper or studio one-pager, not an app UI. Multilingual by design (EN · zh-CN · ja). One self-contained HTML file, zero dependencies.
fs-electric-studio
OpenDesign as an enterprise design platform: a buyer-forwardable proposal for a design-org's economic buyer — pain, value, ROI, rollout. Built as a decision-grade B2B sales deck for economic buyer, design VP, procurement.
hps-bauhaus
A visual-design fundamentals course for new brand designers — grid, type, color, and the exercises that build the eye. Built as a decision-grade professional training deck for junior designers, new hires.
hps-true-blueprint
OpenDesign's engineering blueprint: how the sandbox, sidecar, and daemon fit — the system diagram and the invariants. Built as a decision-grade product management deck for engineering org.
ve-terminal-mono
OpenDesign from the CLI: driving the full design workflow with the od command — scripted, composable, agent-ready. Built as a decision-grade AI literacy deck for developers, power users.
fs-editorial-forest
Art-directing a fashion house's annual report — the editorial system, the photography rhythm, and the data spreads. Built as a decision-grade design craft deck for brand stakeholders, exec audience.