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 elevanaltd/HestAI-MCP --skill pattern-masterygit clone --depth 1 https://github.com/elevanaltd/HestAI-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/elevanaltd/hestai-mcp/pattern-mastery)<a href="https://agentmods.dev/skills/elevanaltd/hestai-mcp/pattern-mastery"><img src="https://agentmods.dev/badge/skills/elevanaltd/hestai-mcp/pattern-mastery/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/elevanaltd/hestai-mcp/pattern-mastery"><img src="https://agentmods.dev/badge/skills/elevanaltd/hestai-mcp/pattern-mastery.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.00000 | $0.00497 |
| Opus 5 | $0.00000 | $0.00249 |
| Sonnet 5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
pattern-mastery 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.
What it actually says
===SKILL:PATTERN_MASTERY=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Identify, name, and apply cross-domain and synthesis patterns with evidence." REQUIRES::[octave-literacy, octave-mastery]
§1::PATTERN_LIBRARY BREAKTHROUGH_PATTERNS::[ CONSTRAINT_INVERSION::"The limitation IS the feature - flip the constraint", DOMAIN_COLLISION::"Borrow brilliance from unrelated fields", SUBTRACTION_INNOVATION::"Remove to improve", PERSPECTIVE_SHIFT::"Solve it like an expert from another field", EDGE_CASE_ELEVATION::"Exceptions reveal the deeper rule", PATTERN_TRANSPLANT::"Reuse proven pattern from X to Y" ] SYNTHESIS_PATTERNS::[ CONSTRAINT_AS_CATALYST::"Wall's limit powers Wind's vision", PHASED_APPROACH::"Temporal separation of vision vs constraint", SCOPE_SPLIT::"Context-specific solutions", ABSTRACTION_LIFT::"Higher-level frame dissolves conflict", TEMPORAL_SEPARATION::"Now vs later resolves tension", INVERSION_SYNTHESIS::"The constraint becomes the solution" ]
§2::METHOD STEPS::[ MAP_TENSION::"Name the opposing forces or constraints", SCAN_LIBRARY::"Select candidate patterns from BREAKTHROUGH_PATTERNS ⧺ SYNTHESIS_PATTERNS", EVIDENCE_CHAINS::"For each chosen pattern, cite 3+ concrete examples (≥1 cross-domain)", NAME_IT::"State the pattern explicitly in outputs", EMERGENCE_PROOF::"Show 1+1=3 effect when applying the pattern", HANDOFF::"State how the pattern guides next role (Validator/Synthesizer/Implementer)" ]
§3::RULES MUST::[ "Always name the pattern applied", "Provide evidence chains (3+ examples, ≥1 cross-domain)", "Show how the pattern transforms the constraint", "Keep scope inside stated boundaries" ] MUST_NEVER::[ "Offer pattern without naming it", "Speculate without evidence", "Use pattern as tiebreaker instead of synthesis", "Expand scope beyond given constraints" ]
===END===
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 · 51 lines · 0 tokens per session scan A a0f0213a7278
pattern-mastery is a skill published in the GitHub repository elevanaltd/HestAI-MCP (0 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 497 tokens. 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-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…