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/hlalljie/agent-workflow-presets/setupnpx skills add hlalljie/agent-workflow-presets --skill setupgit 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.svg" alt="Measured on agentmods" 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 | $0.00037 | $0.01035 |
| Opus 5 | $0.00018 | $0.00517 |
| Sonnet 5 | $0.00007 | $0.00207 |
| Haiku 4.5 | $0.00004 | $0.00103 |
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 4d 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 — 99 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.
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.
If the project is early-stage and the structure is trivial, keep this short. Do not fabricate folders that don't exist yet.
4. Fill in .cursor/rules/repository-layout.mdc
This rule points at the folder-structure doc plus any domain-specific docs (e.g. docs/auth.md, docs/<domain>/README.md). It also names the reference implementation — the canonical route, module, or component that other features should mirror.
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.
- 4d 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 1mo ago), licensed MIT. It adds 37 tokens to every session and 1,035 once invoked, about $0.0002 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
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
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…
cost-optimization
Optimize cloud costs across AWS, Azure, GCP, and OCI through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.