Borrowing it
Nothing to install: this file belongs to hlalljie/agent-workflow-presets. 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/hlalljie/agent-workflow-presets/main/.cursor/skills/blueprint/generate/SKILL.mdgit clone --depth 1 https://github.com/hlalljie/agent-workflow-presetsWrote 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/hlalljie/agent-workflow-presets/generate)<a href="https://agentmods.dev/skills/hlalljie/agent-workflow-presets/generate"><img src="https://agentmods.dev/badge/skills/hlalljie/agent-workflow-presets/generate/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/hlalljie/agent-workflow-presets/generate"><img src="https://agentmods.dev/badge/skills/hlalljie/agent-workflow-presets/generate.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.00053 | $0.00868 |
| Opus 5.5 | $0.00021 | $0.00347 |
| Sonnet 5.5 | $0.00011 | $0.00174 |
| Haiku 4.5 | $0.00005 | $0.00087 |
Grade A, and why
blueprint-generate 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 19d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blueprint generate
Turn what a project already does into catalog parts, and keep those parts current. Formats, types, sources file, and lock file are in FORMAT.md. Read it first. Applying parts to a project is blueprint-apply, not this skill.
Input
[<type>[/<name>]] [from <project>] [to <catalog alias>] [focus: <type>]. Default source is the current project. Naming a part means Save. Naming no part means Report.
Save (create or update one part)
- Sources. Read
~/.blueprints/sources.md(create it by asking, if missing). - Catalog. Use
to. Otherwise pick by permission: anything naming a client, using client assets, or shaped by a private API goes to that client's catalog; anything generic goes to the personal one. If unclear, ask. - Scope. If the request is too broad to be one part (for example "the stack"), ask which types, and for a type like
frontendordeploy, which pieces. One part is one concern. - Extract with "Where to look" in FORMAT.md. Record decisions and patterns in the fewest words that work. Whitelist only the files that must be copied as-is. Apply "Never include" strictly, and scan what you wrote for key-like strings before saving.
- Write
parts/<type>/<name>/PART.mdandfiles/in the catalog's working tree. If the catalog is empty, also add the shortREADME.mdfrom FORMAT.md. If the part already exists, show what changes as a numbered list first and write only the picked items. - Stop. Do not commit. Tell the user to commit in the catalog repo. Afterward, running
/blueprint-apply <type>=<name>in the project records the lock, since the project already matches.
Judgment
lock.sh and git only list changes. What counts as a part, what is worth pushing, and generic vs repo-specific are your call, and every label is a suggestion for the user to overrule. Read the actual files before labeling. When unsure, ask.
Report (no part named)
Compare the current project against every part in .cursor/blueprints.md, and scan for things worth adding. Show everything unless focus narrows it to one type. Output only this, one numbered line each, most important first, at most about 15 lines (then "and N more"):
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.
- 19d ago First seen · 48 lines · 53 tokens per session scan A c01415c15cee
blueprint-generate is a skill published in the GitHub repository hlalljie/agent-workflow-presets (2 stars, last pushed 20d ago), licensed MIT. It adds 53 tokens to every session and 868 once invoked, about $0.0002 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-10-10.
Other skills, from other repositories
work-on-ticket
Fetches Jira ticket details, creates an appropriately named branch, and initiates the task planning workflow. Use when the user says "work on [TICKETID]" or similar phrases.
cast-plan
Turn a request into a plan the team can review before code exists. Explores the codebase, searches prior sessions and recorded decisions for earlier attempts, interviews the user on the open questions, then writes a codecast plan with tasks and dependencies ready for orchestrate. Use when work has several parts, when…
cast-org
Talk through the organization of agents and people around this work with the person, in this session: who reports to whom, what each role looks after, where their sessions go. Reads what the code and the sessions say before it trusts a plan or a task, asks what the records cannot settle, and posts each agreed change…
cast-handoff
Package the current work so the next session or a teammate can continue without reading this thread. Writes the decisions, the direction, what is verified, open questions and ordered next steps as a shared doc, pins the state, and optionally forks, spawns or hands the work to a session. Use before stopping, before a…
cast-loop
Run an autonomous loop that works through a queue of tasks one fresh session at a time, with verification as the gate and a human decision at merge. Sets up a recurring trigger that spawns a session per ready task, a precheck that spends nothing when the queue is empty, and the rules each run follows. Use for a…
cast-conflicts
Before editing or fanning out work, find the live sessions on this repository that are changing the same files, show what they changed, and warn them. Use before starting a task that touches shared files, before spawning workers, or when asked who else is working on this.