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 Kin9Zeus/senior-engineer-skills --skill project-blueprintgit clone --depth 1 https://github.com/Kin9Zeus/senior-engineer-skillsWrote 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/kin9zeus/senior-engineer-skills/project-blueprint)<a href="https://agentmods.dev/skills/kin9zeus/senior-engineer-skills/project-blueprint"><img src="https://agentmods.dev/badge/skills/kin9zeus/senior-engineer-skills/project-blueprint/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/kin9zeus/senior-engineer-skills/project-blueprint"><img src="https://agentmods.dev/badge/skills/kin9zeus/senior-engineer-skills/project-blueprint.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.00148 | $0.02219 |
| Opus 5 | $0.00074 | $0.01110 |
| Sonnet 5 | $0.00030 | $0.00444 |
| Haiku 4.5 | $0.00015 | $0.00222 |
Grade A, and why
project-blueprint 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 11d 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Blueprint
Anything retrofitted costs five to fifty times what it costs to build in. The order below is not stylistic — it is ordered by the cost of getting it wrong later.
Never start typing code from a one-line brief. Ten minutes of Phase 1 saves weeks. But do not interrogate either: ask the questions whose answers change the architecture, assume sensible defaults for the rest, and state the assumptions.
Phase 1 — Understand what is actually being built
Five questions. Ask only the ones you cannot infer from the brief.
- Who uses it, and how many? Ten internal users and ten million consumers are different systems. If unknown, design for 10k and note the first bottleneck.
- What is the core transaction? The one thing that must never be wrong. Everything else is supporting cast.
- What data does it hold? Specifically: does it hold personal data, payment data, or health/financial records? Each adds non-optional obligations.
- What must it integrate with? Existing systems, auth providers, payment rails, data sources.
- What are the constraints? Team size and skills, budget, deadline, regulatory jurisdiction, self-host vs cloud.
Then write, in five lines: what it is, who it serves, the core transaction, the data classification, and the constraint that dominates. Confirm this before building. Getting the brief wrong is the only unrecoverable error here.
Phase 2 — Choose the stack, and justify it
See references/stack-selection.md for the decision framework.
The default answer is boring, well-supported technology the team already knows. Novelty is a cost paid in hiring, debugging and documentation for the life of the system. Choose novelty only where it is the differentiator.
Decide and record: language and runtime, framework, database, hosting, auth
strategy, CI, monitoring. Each with a one-line reason. These become the first
ADRs — see templates/adr.md.
Refuse to over-engineer. No Kubernetes, no microservices, no event sourcing, no CQRS, no service mesh for a product with no users. A modular monolith on a managed platform with a managed Postgres is the correct answer for the overwhelming majority of new products, and it is the answer that stays cheap to change.
What ships with it
7 files 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.
- 11d ago First seen · 197 lines · 148 tokens per session scan A 584b795007b1
project-blueprint is a skill published in the GitHub repository Kin9Zeus/senior-engineer-skills (3 stars, last pushed 17d ago), licensed MIT. It adds 148 tokens to every session and 2,219 once invoked, about $0.0007 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
ci-cd
Load this skill when configuring or reviewing CI/CD pipelines, GitHub Actions workflows, or automated testing setups. Ensures accessibility regressions are caught before code reaches production by enforcing quality gates, structured reporting, and layered automated + manual testing across all pages and user…
devops-engineer
Creates Dockerfiles, configures CI/CD pipelines, writes Kubernetes manifests, and generates Terraform/Pulumi infrastructure templates. Handles deployment automation, GitOps configuration, incident response runbooks, and internal developer platform tooling. Use when setting up CI/CD pipelines, containerizing…
accessibility
Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".
performance
Optimize web performance for faster loading and better user experience. Use when asked to "speed up my site", "optimize performance", "reduce load time", "fix slow loading", "improve page speed", or "performance audit".
seo
Optimize for search engine visibility and ranking. Use when asked to "improve SEO", "optimize for search", "fix meta tags", "add structured data", "sitemap optimization", or "search engine optimization".
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.