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 isvlasov/rageatc-oss --skill designing-workflowgit clone --depth 1 https://github.com/isvlasov/rageatc-ossWrote 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/isvlasov/rageatc-oss/designing-workflow)<a href="https://agentmods.dev/skills/isvlasov/rageatc-oss/designing-workflow"><img src="https://agentmods.dev/badge/skills/isvlasov/rageatc-oss/designing-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/isvlasov/rageatc-oss/designing-workflow"><img src="https://agentmods.dev/badge/skills/isvlasov/rageatc-oss/designing-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.00031 | $0.00963 |
| Opus 5 | $0.00015 | $0.00481 |
| Sonnet 5 | $0.00006 | $0.00193 |
| Haiku 4.5 | $0.00003 | $0.00096 |
Grade A, and why
designing-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 10d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Designing Workflow
The canonical six-phase menu for rageatc-core-oss — every workflow subsets from these phases based on task characteristics. This skill covers structure (which phases, when); execution (agent coordination, logging, validation) lives in orchestrating-work.
Phase Menu
Phase 1: Preparation (always)
Understand requirements, explore context, identify the execution approach. The full arc is Ideate → Understand → Solution → Brief, each step optional:
ideating— generate and explore ideas when the user doesn't yet have a clear taskunderstanding-the-ask— explore user intent through structured dialoguesolutioning— explore solution options when the approach is unclear- Exploratory research via subagents, reading referenced documents, clarifying ambiguities and constraints
Outputs: clear understanding of requirements; decision record if solutioning was used; captured ideas if ideating was used.
Phase 2: Planning (always — spend the most user time here)
Create the execution plan for orchestrator and user — NOT for agents, who receive instructions at invocation. Leverage the plan agent, review the plan with the user, identify decision points, dependencies, agent sequence, and file paths. If planning is done right, everything else flows smoothly.
Output: work/<task-id>/plan.md.
Phase 3: Research (optional)
Background investigation, fact-finding, evidence gathering. Include for novel domains, unfamiliar problem spaces, or factual claims needing verification; skip for routine well-understood work or when the necessary knowledge is already in context.
Sub-steps: research brief (orchestrator-owned, per creating-briefs) → execute (researcher / source-collector) → fact-check (optional but recommended) → review (critic, iterate if needed).
Outputs: research document, source index (thorough mode), fact-check report.
Research is the primary fact-checking checkpoint — verify claims here to prevent error propagation into artefacts.
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.
- 10d ago First seen · 82 lines · 31 tokens per session scan A 009f4a0f99f4
designing-workflow is a skill published in the GitHub repository isvlasov/rageatc-oss (9 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 963 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
design-method
Use when starting any design task — resolves register, sets the 3 dials, locks Gate 0, and routes to the right move and target skill.
design-webapp
Use when building or extending a dashboard, SaaS screen, or any authenticated app surface — use design-web instead for a marketing site.
design-web
Use when building or revising a marketing/landing/campaign page, register brand locked at Gate 0 — use design-webapp for app screens instead.
fusecore
Use when creating modules, understanding FuseCore structure, or implementing features in a FuseCore modular-monolith Laravel project.
laravel-architecture
Use when structuring a Laravel project, creating services/repositories/actions, implementing dependency injection, or organizing code layers.
laravel-auth
Use when implementing user authentication, API tokens, social login, or authorization in Laravel 13.