engineering-workflow

engineering-workflow is a skill for Codex from polaralias/skills. It costs 84 tokens per session (1,227 once invoked), scanned A, original, Apache-2.0.

A repository engineering workflow for understanding, planning, changing, testing, documenting, reviewing, and coordinating substantial software work.

In plain words
What is it for?
It is for implementing features, fixing bugs, refactoring, testing, reviewing, documenting, resuming, checkpointing, and closing engineering tasks.
Why use it?
It provides a consistent process for material changes and records workflow state before edits, helping distinguish completed work from work that was only planned.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit It is for implementing features, fixing bugs, refactoring, testing, reviewing, documenting, resuming, checkpointing, and closing engineering tasks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/polaralias/skills/engineering-workflow
Install

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.

Any agent
npx skills add polaralias/skills --skill engineering-workflow
Clone the repo
git clone --depth 1 https://github.com/polaralias/skills

Made for: Codex.

Wrote 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.

agentmods badge for engineering-workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/polaralias/skills/engineering-workflow/github.svg)](https://agentmods.dev/skills/polaralias/skills/engineering-workflow)
Your own site
<a href="https://agentmods.dev/skills/polaralias/skills/engineering-workflow"><img src="https://agentmods.dev/badge/skills/polaralias/skills/engineering-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.

agentmods 80×15 button for engineering-workflow

Your own site · 80×15
<a href="https://agentmods.dev/skills/polaralias/skills/engineering-workflow"><img src="https://agentmods.dev/badge/skills/polaralias/skills/engineering-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 84 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,227 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00084 $0.01227
Opus 5.5 $0.00034 $0.00491
Sonnet 5.5 $0.00017 $0.00245
Haiku 4.5 $0.00008 $0.00123

Measured 18d ago against content hash d37158a2a472, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

engineering-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 18d 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.

skills/engineering/engineering-workflow/SKILL.md · 55 lines

How it starts

The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Engineering Workflow

Select the engineering method that fits the user's immediate need, read its reference, and perform the work. Use the entry point to select the current method and its required outcome. Read only the relevant references.

Select a method

Need Read
Explain code, behaviour, a diff, or what changed Comprehension
Make an inherited, unclear, or undocumented repository legible Dissection
Resolve terminology, contradictory claims, or consequential intent Clarification
Turn a resolved outcome into contracts, scenarios, acceptance, and work packages Design
Implement, fix, refactor, test, or review a bounded code change Delivery
Establish, capture, review, align, or streamline canonical repository knowledge Knowledge
Maintain durable tasks, workstreams, effort, and execution evidence Task lifecycle
Reconcile material work before claiming completion Alignment
Preserve unfinished work across a pause or session boundary Handoff
Resume and verify continuation evidence Pickup
Allocate parallel ownership, branches, worktrees, integration, or cleanup Coordination
Assess release readiness, review publication safety, or publish accepted work to a tracker Publication

The reference map shows conditional transitions between methods. Initial repository bootstrap remains outside this workflow.

Work proportionately

For a bounded correction: inspect the named source and relevant tests, fix it, run focused validation, review documentation impact as described in delivery, and explain the causal result. Do not create tasks, knowledge bundles, persistent workflow state, handoffs, or a release review merely to finish a small change. Honour existing repository obligations and report material limitations.

Read the full file on GitHub · 55 lines

Changes

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.

  1. 18d ago Changed · +4 lines d37158a2a472
  2. 19d ago Changed · -126 lines · -34 tokens per session efb9f15618fa
  3. 1mo ago Changed · +12 lines 7d959f2ed488
  4. 1mo ago First seen · 165 lines · 118 tokens per session scan A b742611f3b15

Subscribe to this mod's changes

engineering-workflow is a skill published in the GitHub repository polaralias/skills (2 stars, last pushed 10d ago), licensed Apache-2.0. It adds 84 tokens to every session and 1,227 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-09-19.

Related

engineering-workflow compared with skills from other repositories

engineering-workflow next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
engineering-workflowpolaralias/skillsSkill210d agoApache-2.0A84Codex
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79kyesterdayMITA200Claude Code, Codex
playwright-climicrosoft/playwrightSkill100kyesterdayApache-2.0A19Claude Code
browser-automationopenclaw/openclawSkill394ktodayMITA36Claude Code
systematic-debuggingobra/superpowersSkill314k4d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code