A routing guide for engineering workflows that are not tied to one programming language. It covers architecture, shell work, tool connections, prototypes, planning, issue breakdown, skill authoring, and release notes.

Use it to make architecture decisions, plan delivery, break work into issues, build MCP or command-line tools, prototype, write agent skills, or prepare release communication.

It helps select only the instructions needed for the current engineering task. This reduces unrelated guidance when a project spans several kinds of work.

engineering — Skill for Claude Code and Codex by heyAyushh/stacc

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 heyAyushh/stacc --skill engineering

Clone the repo

git clone --depth 1 https://github.com/heyAyushh/stacc

Made for: Claude Code, 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/heyayushh/stacc/engineering/github.svg)](https://agentmods.dev/skills/heyayushh/stacc/engineering)

Your own site

<a href="https://agentmods.dev/skills/heyayushh/stacc/engineering"><img src="https://agentmods.dev/badge/skills/heyayushh/stacc/engineering/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/heyayushh/stacc/engineering"><img src="https://agentmods.dev/badge/skills/heyayushh/stacc/engineering.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 165 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.

Model	Per session	Once invoked
Fable 5.1	$0.00038	$0.00165
Opus 5.5	$0.00015	$0.00066
Sonnet 5.5	$0.00008	$0.00033
Haiku 4.5	$0.00004	$0.00016

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

Security

Grade A, and why

engineering 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 26d ago.

The scan reads SKILL.md. This mod also ships 2 executable files (mcp-builder/scripts/connections.py, mcp-builder/scripts/evaluation.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

configs/stacks/engineering/SKILL.md · 19 lines

What it actually says

Engineering workflow stack

Load only the branch needed for the current task:

Architecture and design decisions: improve-codebase-architecture, grill-with-docs, or prototype.
Delivery planning: to-prd, to-issues, or triage.
Tool construction: mcp-builder, cli-for-agents, or bash-expert.
Skill authoring: write-a-skill.
Release communication: changelog-generator.

Read the selected child SKILL.md; its completion criteria own that workflow.

Files

What ships with it

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

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.

26d ago First seen · 19 lines · 38 tokens per session scan A 7a46394f38ef

Subscribe to this mod's changes

engineering is a skill published in the GitHub repository heyAyushh/stacc (3 stars, last pushed 26d ago), licensed MIT. It adds 38 tokens to every session and 165 once invoked, about $0.0002 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-22.

Planning

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

component-fixtures

Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.