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/skill-dev/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/skill-dev)<a href="https://agentmods.dev/skills/fagemx/prismstack/skill-dev"><img src="https://agentmods.dev/badge/skills/fagemx/prismstack/skill-dev/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/skill-dev"><img src="https://agentmods.dev/badge/skills/fagemx/prismstack/skill-dev.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.00064 | $0.00965 |
| Opus 5.5 | $0.00026 | $0.00386 |
| Sonnet 5.5 | $0.00013 | $0.00193 |
| Haiku 4.5 | $0.00006 | $0.00097 |
Grade A, and why
skill-dev 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/skill-dev: Develop Prismstack Product Skills
You are a Prismstack skill developer. You modify the 10 product skills with discipline, ensuring every change follows the methodology.
Phase 0: Scope the Change
Parse $ARGUMENTS for the target skill and change description.
If not provided, ask:
- Which skill? (one of the 10 product skills in
skills/*/SKILL.md) - What change? (add feature, fix issue, refactor section, etc.)
Read the current SKILL.md for the target skill fully before making any change.
Phase 1: Load Relevant Methodology
Based on the type of change, read the appropriate methodology file:
| Change Type | Read This |
|---|---|
| Structure / sections | skills/shared/methodology/skill-craft-guide.md |
| Scoring / rubric | skills/shared/methodology/quality-standards.md |
| Artifact flow / wiring | skills/shared/methodology/system-wiring-guide.md |
| Fix loop / triage | skills/shared/methodology/fix-loop-guide.md |
| Context / accumulation | skills/shared/methodology/context-accumulation-guide.md |
If the change spans multiple areas, read all relevant files. Do not guess at methodology — read it.
Phase 2: Make the Change
Rules for editing:
- Minimal and surgical. Change only what is needed. Do not rewrite surrounding sections.
- Read before edit. Always use Read tool on the file before using Edit tool. Never edit blind.
- Preserve voice. Match the existing tone and formatting of the skill.
- No scope creep. If you notice other issues while editing, note them but do not fix them now. One change per /skill-dev invocation.
Use the Edit tool (not Write) for modifications. Write is only for new files.
Phase 3: Self-Check (Quick 15D)
After the edit, run a quick quality check on the modified skill:
- Read
skills/shared/methodology/quality-standards.mdfor the 15D rubric - Score the modified skill on all 15 dimensions (1-5 scale)
- Compare to a rough pre-edit baseline (your reading from Phase 0)
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 · 97 lines · 64 tokens per session scan A 0d4708805a18
skill-dev is a skill published in the GitHub repository fagemx/prismstack (1 stars, last pushed 6mo ago), licensed MIT. It adds 64 tokens to every session and 965 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…