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 quatico-solutions/agent-skills --skill adopt-agentic-workflowgit clone --depth 1 https://github.com/quatico-solutions/agent-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/quatico-solutions/agent-skills/adopt-agentic-workflow)<a href="https://agentmods.dev/skills/quatico-solutions/agent-skills/adopt-agentic-workflow"><img src="https://agentmods.dev/badge/skills/quatico-solutions/agent-skills/adopt-agentic-workflow/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/quatico-solutions/agent-skills/adopt-agentic-workflow"><img src="https://agentmods.dev/badge/skills/quatico-solutions/agent-skills/adopt-agentic-workflow.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.00076 | $0.01858 |
| Opus 5 | $0.00038 | $0.00929 |
| Sonnet 5 | $0.00015 | $0.00372 |
| Haiku 4.5 | $0.00008 | $0.00186 |
Grade A, and why
adopt-agentic-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 9d 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adopt the Four-Phase Agentic Workflow
Set up Discovery → Design → Development → Endgame in a repository: the plan lifecycle, plus the skills that serve each phase.
What this does, and what it delegates
Plot owns the plan lifecycle. It is project-agnostic by design, so it knows
nothing about this organisation's tooling. Its /plot-init probes the repo and
sets up plans, branches, and config — this skill does not reimplement any of
that.
This skill owns the connective layer: which of our skills serves which phase, where our Definition of Done lives, and how session logs get written. That mapping is the thing a newcomer (human or agent) cannot infer, and it is what turns a set of installed skills into a workflow.
The dependency runs one way. This skill knows Plot; Plot must never know this skill. If Plot changes, adjust here — not there.
Prerequisites
Plot must be available (plugin, pnpm dlx skills add, or a symlink into
~/.claude/skills/). If /plot-init is not available, say so plainly and
stop: the phases below are all anchored to plan states, so there is nothing
useful to install without it.
Steps
1. Run Plot's own adoption
/plot-init
It probes the repo (git host, quality-gate scripts, ticket scheme, commit
notation, existing planning systems) and proposes a ## Plot Config. Let it
run to completion and let the user confirm its proposals — do not answer on
their behalf, especially the Definition of Done: /plot-init finds
candidate scripts, but only a human knows which gate a merge.
If /plot-init reports that a Plot Config already exists, skip to step 2. This
skill is additive over an existing Plot setup.
2. Write the phase-to-skill map into the hub
This is the core of this skill. Append to the hub doc (CLAUDE.md or
AGENTS.md — whichever /plot-init used), adapted to what the repo actually
has. Only list skills that exist here; a map pointing at absent tools is
worse than no map.
## Agentic Workflow
Four phases, each turning one durable artifact into the next.
| Phase | Produces | Commands and skills |
|-------|----------|---------------------|
| **Discovery** | a story (`docs/stories/`) or a ticket assessment | `triage-ticket` for an incoming ticket · `story-tracking` for multi-session work |
| **Design** | an approved plan (`docs/plans/`) | `/plot-idea` → `challenge-the-plan` → `/plot-approve` |
| **Development** | merged branches | `/plot-implement` · `test-driven-development` · `commit-notation` · `handling-pull-requests` → `/plot-deliver` |
| **Endgame** | a verified release | `reality-check` before claiming done · `/plot-release rc` → verify the checklist → `/plot-release` |
Discovery is optional: small, well-understood work goes straight to Design.
**Plans vs. session logs.** A plan says what will be built and is frozen on
approval. A session log says how it was decided — including the alternatives
that were rejected — stays amendable, and outlives the plan. If it must be
true *before* building starts, it belongs in the plan; if it answers "why not
the other way?", it belongs in a log.
What ships with it
1 file 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.
- 9d ago First seen · 176 lines · 76 tokens per session scan A 29f36c1df0ed
adopt-agentic-workflow is a skill published in the GitHub repository quatico-solutions/agent-skills (2 stars, last pushed 5d ago), licensed MIT. It adds 76 tokens to every session and 1,858 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…