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 KiranEswaran/engineering-skills --skill agent-workflowgit clone --depth 1 https://github.com/KiranEswaran/engineering-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/kiraneswaran/engineering-skills/agent-workflow)<a href="https://agentmods.dev/skills/kiraneswaran/engineering-skills/agent-workflow"><img src="https://agentmods.dev/badge/skills/kiraneswaran/engineering-skills/agent-workflow.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.1 | $0.00069 | $0.00833 |
| Opus 5 | $0.00034 | $0.00417 |
| Sonnet 5 | $0.00014 | $0.00167 |
| Haiku 4.5 | $0.00007 | $0.00083 |
Grade A, and why
agent-workflow 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 7d 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.
Agent Workflow
Golden Rules
Follow this three-phase approach for all non-trivial work:
- PLAN → Design solution → Document approach → WAIT FOR EXPLICIT APPROVAL
- IMPLEMENT → Code ONLY what was approved → STOP when agreed scope is complete
- REVIEW → Verify results → Suggest improvements → Return to PLAN phase
Critical Violations to Avoid
- DON'T DO THIS:
User: "Can you add authentication?"
AI: [Immediately starts coding without discussion]
+ DO THIS INSTEAD:
User: "Can you add authentication?"
AI: "Let me design a solution first. Key decisions needed:
- OAuth 2.0 vs local authentication?
- JWT tokens vs session-based?
- User data storage location?
Let's agree on the approach before I write any code."
Why This Matters:
- Skipping planning → Wasted time, wrong solutions, scope creep
- Implementing unplanned features → Breaking existing code, technical debt
- Not stopping after agreed scope → Confusion, frustration, rework
Complexity Levels
| Level | Type | Workflow | Example |
|---|---|---|---|
| 1 | Simple | Direct implementation → Quick review | Fix typo, simple bug fix |
| 2 | Moderate | Brief plan → QA → Implement → Review | Add new function |
| 3 | Complex | Full Plan → Creative → QA → Implement → Review | Multi-file feature |
| 4 | Architectural | Detailed Plan → Creative (mandatory) → QA → Implement → Review | Major refactoring |
Phase 1: Planning
You MUST NOT begin implementation until:
- User has explicitly approved the plan
- All clarifying questions have been answered
- The scope is clearly defined and agreed upon
Process:
- Analyze the request - understand scope, constraints, requirements
- Check existing code - look for patterns and reusable components
- Design the solution - propose approach with alternatives
- WAIT FOR APPROVAL - present plan and await confirmation
What ships with it
2 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.
- 7d ago First seen · 102 lines · 69 tokens per session scan A 69b8f25cd9d3
agent-workflow is a skill published in the GitHub repository KiranEswaran/engineering-skills (10 stars, last pushed 8mo ago), licensed MIT. It adds 69 tokens to every session and 833 once invoked, about $0.0003 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.