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/setup/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/setup)<a href="https://agentmods.dev/skills/hlalljie/agent-workflow-presets/setup"><img src="https://agentmods.dev/badge/skills/hlalljie/agent-workflow-presets/setup/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/setup"><img src="https://agentmods.dev/badge/skills/hlalljie/agent-workflow-presets/setup.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.00037 | $0.01208 |
| Opus 5.5 | $0.00015 | $0.00483 |
| Sonnet 5.5 | $0.00007 | $0.00242 |
| Haiku 4.5 | $0.00004 | $0.00121 |
Grade A, and why
setup 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup
When to use
Once per project, right after copying the agent-presets contents into a new repository. After this runs, the skill can be deleted from the project — it has no ongoing use.
Job
Walk the project owner through filling in every <!-- TODO: --> marker across .cursor/ and docs/, asking questions as needed, and writing the answers back into the right files. End with a clean, project-specific agent configuration.
Process
1. Survey the project first
Before asking anything, read what the project already has:
package.json— name, framework, runtime versions, scripts- Top-level folders — what's in
src/,tests/,docs/, any others - Any existing README or architecture docs
You need enough context to make informed suggestions when asking the owner fill-in questions. Do not ask things the codebase already answers.
1b. Offer blueprints (optional)
If ~/.cursor/skills/blueprint/apply/SKILL.md exists (installed per machine, see the README), ask the owner once: scaffold any parts (api, database, cache, branding, plan, and so on) from blueprints or another project? If yes, read that file and follow it with their scaffold line before the TODO pass, since applied parts can fill some TODOs. The skill is slash-only, so you cannot invoke it by name; read the file instead. If no, or the file is missing, skip this step.
2. Find every TODO
Run:
grep -rn "TODO:" .cursor/ docs/
This is the canonical list of fill-ins. Work through them in this order (dependencies first):
docs/folder-structure.md— everything else references it.cursor/rules/repository-layout.mdc— points at the doc above.cursor/rules/nextjs.mdc— or delete if not a Next.js project- Any others that appear
3. Fill in docs/folder-structure.md
This is the most important file. Propose a draft based on the survey in step 1, then confirm with the owner before writing.
For each top-level folder under src/, write one bullet explaining what lives there. If the structure is genuinely complex (multiple routes, services, widgets with a shared pattern), include a "read order" guide for the most common "add a new X" task.
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 Changed · +3 lines 228c8bf2c526
- 1mo ago First seen · 99 lines · 37 tokens per session scan A 638a1e4745d9
setup is a skill published in the GitHub repository hlalljie/agent-workflow-presets (2 stars, last pushed 20d ago), licensed MIT. It adds 37 tokens to every session and 1,208 once invoked, about $0.0001 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
curate-a-team-library
Use when building a managed team skills library for a real stack. Map work to shelves, browse before curating, write meaningful whyHere notes, and create a starter pack once the first pass is solid.
review-a-skill
Use when evaluating whether a skill belongs in a library. Preview content, check frontmatter, validate structure, and decide whether to keep, curate, or remove.
audit-library-health
Use when checking the overall health of a skills library. Run doctor, validate, check for stale skills, and verify generated docs are in sync.
share-a-library
Use when a managed library is ready to publish to GitHub and hand to teammates as an install command. Run the GitHub publishing steps, then return the exact shareable install command.
build-workspace-docs
Use when regenerating README.md and WORKAREAS.md in a managed library workspace. Always dry-run first to preview changes.
update-installed-skills
Use when syncing or updating previously installed skills to their latest version. Always dry-run updates before applying, and check for breaking changes.