Borrowing it
Nothing to install: this file belongs to fagemx/prismstack. 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/fagemx/prismstack/main/.claude/skills/methodology-sync/SKILL.mdgit clone --depth 1 https://github.com/fagemx/prismstackWrote 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/fagemx/prismstack/methodology-sync)<a href="https://agentmods.dev/skills/fagemx/prismstack/methodology-sync"><img src="https://agentmods.dev/badge/skills/fagemx/prismstack/methodology-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/fagemx/prismstack/methodology-sync"><img src="https://agentmods.dev/badge/skills/fagemx/prismstack/methodology-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.00065 | $0.00911 |
| Opus 5.5 | $0.00026 | $0.00364 |
| Sonnet 5.5 | $0.00013 | $0.00182 |
| Haiku 4.5 | $0.00006 | $0.00091 |
Grade A, and why
methodology-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 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/methodology-sync: Find Drift Between Docs and Implementation
You are a consistency auditor. Your job is to find drift between what Prismstack's methodology documents promise and what the 10 product skills actually implement.
Phase 1: Load All Methodology Files
Read all files in skills/shared/methodology/:
ls skills/shared/methodology/*.md
Expected files (5):
skill-craft-guide.md— principles and how-to's for building skillsquality-standards.md— the 15D scoring rubricsystem-wiring-guide.md— artifact flow, discovery, save patternsfix-loop-guide.md— baseline → triage → fix → re-score workflowcontext-accumulation-guide.md— signals for cross-skill context
Read each one fully. Extract every concrete claim, requirement, or pattern it defines. Keep a running list of "methodology promises."
Phase 2: Check Implementation in Skills
For each methodology promise, search the 10 product skills for implementation.
Specific Checks
From skill-craft-guide:
- Claims "8 principles" → list them, grep each skill for evidence of each principle
- Claims "10 how-to's" → verify /domain-build references all relevant how-to's
- Any structural requirement (e.g., "every skill must have X section") → check all 10
From quality-standards:
- Claims "15D" rubric → verify /skill-check actually scores all 15 dimensions
- Each dimension has specific criteria → verify /skill-check uses them, not a simplified version
From system-wiring-guide:
- Claims "artifact flow" pattern → verify every skill has both discovery (read prior artifacts) and save (write artifacts for downstream)
- Claims specific file paths or naming conventions → verify skills use them
From fix-loop-guide:
- Claims "baseline → triage → fix → re-score" flow → verify /skill-check implements all 4 steps
- Claims specific triage rules → verify they appear in the skill
From context-accumulation-guide:
- Claims "4 signals" for context → list them
- Verify all skill completions include context extraction using those signals
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 · 90 lines · 65 tokens per session scan A 644771e958f1
methodology-sync is a skill published in the GitHub repository fagemx/prismstack (1 stars, last pushed 6mo ago), licensed MIT. It adds 65 tokens to every session and 911 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-08-31.
Other skills, from other repositories
technical-documentation
Audit, write, and improve developer documentation using Google's Developer Documentation Style Guide and Technical Writing courses. Use this skill for any documentation work, even when the user names no style guide: "audit our docs", "review this README", "write a README", "getting started guide", "how-to or…
top-design
Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions "Awwwards quality", "make my site stunning", "scroll animations", "parallax storytelling", "cinematic web design", "portfolio site", or "brand experience". Also trigger when elevating a standard…
crossing-the-chasm
Navigate the technology adoption lifecycle from early adopters to mainstream market. Use when the user mentions "crossing the chasm", "beachhead segment", "whole product", "early adopters vs mainstream", "tech go-to-market", "bowling pin strategy", "technology adoption lifecycle", "pragmatist buyers", "growth stalled…
design-everyday-things
Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models. Use when the user mentions "why is this confusing", "affordance", "error prevention", "discoverability", "human-centered design", "mental model", "mapping", "seven stages of action", "users keep making…
design-sprint
Run a structured 5-day process to prototype, test, and validate product ideas with real users. Use when the user mentions "design sprint", "validate before we build", "rapid prototype", "test with users", or "should we build this". Also trigger when a team is stuck in endless debate over a high-stakes product…
hooked-ux
Design habit-forming product loops using the Hook Model (Trigger, Action, Variable Reward, Investment). Use when the user mentions "users arent coming back", "habit formation", "engagement loops", "habit zone", or "the manipulation matrix". Also trigger when designing notification or re-engagement strategies, building…