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 agentmods add skills/devdannnny/chisel/prompt-architectnpx skills add Devdannnny/chisel --skill prompt-architectgit clone --depth 1 https://github.com/Devdannnny/chiselWhat 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 | $0.00156 | $0.02049 |
| Opus 5 | $0.00078 | $0.01025 |
| Sonnet 5 | $0.00031 | $0.00410 |
| Haiku 4.5 | $0.00016 | $0.00205 |
Grade A, and why
prompt-architect 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 2d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prompt Architect
This skill turns a rough human prompt into a professionally structured one using a single, scalable framework called the Prompt Architecture Standard (PAS).
The same framework works for a non-technical request ("write me a birthday speech") and a complex technical/agentic task ("refactor this service, don't touch the API"). It scales by adding or dropping sections — the structure never changes, only the depth.
The job
Given a rough prompt, produce a clean structured prompt. Do not execute the task in the rough prompt — restructure it. The deliverable is a better prompt, not the answer to it.
Workflow
Follow these steps in order.
1. Extract intent
Read the rough prompt fully. Identify, in your own notes: the real goal, the implied audience/executor (a human? an AI agent? a coding tool?), any constraints stated or implied, and any concrete details that must be preserved verbatim (file names, values, names, URLs, exact wording).
2. Classify the task
Pick one:
- Simple / non-technical — a single creative or informational ask (write, summarize, explain, brainstorm). Use Tier 1 sections.
- Technical / agentic — a multi-step task with constraints, a defined target, or code/file changes. Use Tier 1 + Tier 2 sections.
- High-stakes / complex — agentic work where mistakes are costly, scope creep is a risk, or output must be auditable. Use all tiers.
When in doubt, go one tier higher — extra structure rarely hurts.
3. Map content into sections
Place every piece of the rough prompt into the correct PAS section (defined below). Nothing from the original should be silently dropped. If the user listed specific values, statuses, or replacements, preserve them exactly inside the relevant section.
4. Fill gaps and flag assumptions
Rough prompts are usually missing a role, an explicit output format, or success criteria. Add sensible defaults, but never invent constraints the user didn't imply. Mark anything you inferred so the user can correct it.
What ships with it
1 file 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.
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.
- 2d ago First seen · 192 lines · 156 tokens per session scan A baec6b698be2
prompt-architect is a skill published in the GitHub repository Devdannnny/chisel (3 stars, last pushed 2mo ago), licensed MIT. It adds 156 tokens to every session and 2,049 once invoked, about $0.0008 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
screen-reader-testing
Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
team-communication-protocols
Structured messaging protocols for agent team communication including message type selection, plan approval, shutdown procedures, and anti-patterns to avoid. Use this skill when establishing communication norms for a newly spawned team, when deciding whether to send a direct message or a broadcast, when a team-lead…
multi-reviewer-patterns
Coordinate parallel code reviews across multiple quality dimensions with finding deduplication, severity calibration, and consolidated reporting. Use this skill when organizing multi-reviewer code reviews, calibrating finding severity, or consolidating review results.
parallel-debugging
Debug complex issues using competing hypotheses with parallel investigation, evidence collection, and root cause arbitration. Use this skill when debugging bugs with multiple potential causes, performing root cause analysis, or organizing parallel investigation workflows.
task-coordination-strategies
Decompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress.