Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/calionauta/stelownpx agentmods add skills/calionauta/stelow/stelow-workflow-tech-planningWrote 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/calionauta/stelow/stelow-workflow-tech-planning)<a href="https://agentmods.dev/skills/calionauta/stelow/stelow-workflow-tech-planning"><img src="https://agentmods.dev/badge/skills/calionauta/stelow/stelow-workflow-tech-planning/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/calionauta/stelow/stelow-workflow-tech-planning"><img src="https://agentmods.dev/badge/skills/calionauta/stelow/stelow-workflow-tech-planning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 86 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Excessive Agency · line 530 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00087 | $0.04567 |
| Opus 5.5 | $0.00035 | $0.01827 |
| Sonnet 5.5 | $0.00017 | $0.00913 |
| Haiku 4.5 | $0.00009 | $0.00457 |
Grade A, and why
stelow-workflow-tech-planning 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 — 450 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tech Planning Sequencing
Tools: See
../stelow-workflow-orchestrator/references/cli-tools/subagents.mdfor subagent patterns,../stelow-workflow-orchestrator/references/cli-tools/goals.mdfor goal commands.
This skill executes the Tech Planning phase.
How to Load
Via Orchestrator (recommended)
The orchestrator reads this file directly when needed.
Standalone
This skill works standalone. Use the Input Detection section below to tell the skill what technical context to plan from. Follow the instructions inline.
Prerequisites
Security check: Read the YAML frontmatter of spec-product.md:
head -10 spec-product_{v}.md | grep "approved:"
- ✅
approved: true→ proceed - ❌ No
approved: true→ GO BACK to Gate stage (visual review visual review). Do not proceed.
This check is deterministic — does not depend on memory.
AI-Aware Testing Check
For software products, also check product_type:
head -10 spec-product_{v}.md | grep "product_type:"
- ✅
product_type: softwareorproduct_type: hybrid→ activate stelow-workflow-testing-ai-code - ❌
product_type: service→ skip testing strategy
References Index
Read the references/ files to guide the process:
| File | Covers | When to read |
|---|---|---|
references/tech-context.md |
Tech planning context, prerequisites, workflow position | Before starting — sets planning context |
references/scopes-and-sequencing.md |
Scope types (feature/optimization/spike + test-*), executor routing, sequencing principles | During generation — defines scope structure |
references/tech-output.md |
Tech plan output format, frontmatter, receipts | After generation — formats output |
stelow-workflow-coding-standards (skill) |
Universal coding standards (KISS, DRY, LoB, SoC, Fail Fast, YAGNI) | During generation — guides implementation |
How scopes & tasks flow between planning and execution
The split (Shape Up hill chart collapsed into scopes):
What ships with it
7 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.
- 10d ago Changed · +10 tokens per session 26bf67709d83
- 14d ago Changed · +5 lines 8c06ed56ff1f
- 18d ago Changed 48100e72976c
- 28d ago Changed fc9240d3cefc
- 1mo ago Changed · -1 lines c215782521ed
- 1mo ago Changed · +6 lines 87d87e7765c7
- 1mo ago Changed · +41 lines 9690d0c133c5
- 1mo ago Changed · +5 lines ccd8174e5643
- 1mo ago Changed · -255 lines 45d310a6e240
- 2mo ago First seen · 649 lines · 77 tokens per session scan A 6f051d49ea70
stelow-workflow-tech-planning is a skill published in the GitHub repository calionauta/stelow (14 stars, last pushed 9d ago), licensed MIT. It adds 87 tokens to every session and 4,567 once invoked, about $0.0003 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-30.
stelow-workflow-tech-planning compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| stelow-workflow-tech-planningcalionauta/stelow | Skill | 14 | 9d ago | MIT | A | 87 | Claude Code, Codex |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 103 | Claude Code |