everything-claude-code: Skill for Claude Code

.kiro/skills/agentic-engineering/SKILL.md

agentic-engineering is a skill for Claude Code, Kiro from mit-network/everything-claude-code. It costs 40 tokens per session (862 once invoked), scanned A, a copy of agentic-engineering, MIT.

A working method for software projects where AI agents do much of the implementation and people set quality and risk controls.

In plain words
What is it for?
Use it to break projects into independently checkable tasks, test behavior before and after changes, and route work according to its complexity.
Why use it?
It replaces vague agent work with clear completion checks, smaller tasks, appropriate model choices, and tests that reveal regressions.

Skill for Claude CodeKiro

Written for Claude Code and Kiro: shipped in a Claude Code plugin, but also installed under .kiro/.

This is mit-network/everything-claude-code's own configuration. It tells Claude Code and Kiro how to work on everything-claude-code itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything everything-claude-code configures →

Part of the everything-claude-code plugin — 39 skills, 3 commands, 16 agents shipped together

Reuse

Borrowing it

Nothing to install: this file belongs to mit-network/everything-claude-code. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/mit-network/everything-claude-code/main/.kiro/skills/agentic-engineering/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/mit-network/everything-claude-code

Made for: Claude Code, Kiro.

Or install everything-claude-code, the plugin that ships this one along with the rest of its 39 skills, 3 commands, 16 agents.

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 agentic-engineering

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

agentmods 80×15 button for agentic-engineering

Your own site · 80×15
<a href="https://agentmods.dev/skills/mit-network/everything-claude-code/agentic-engineering"><img src="https://agentmods.dev/badge/skills/mit-network/everything-claude-code/agentic-engineering.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 862 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 100% copy Near-identical to another mod 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.00040 $0.00862
Opus 5.5 $0.00016 $0.00345
Sonnet 5.5 $0.00008 $0.00172
Haiku 4.5 $0.00004 $0.00086

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

Security

Grade A, and why

agentic-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 1mo 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.

Origin

This is a copy

100% identical to agentic-engineering — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.kiro/skills/agentic-engineering/SKILL.md · 136 lines

How it starts

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

Agentic Engineering

Use this skill for engineering workflows where AI agents perform most implementation work and humans enforce quality and risk controls.

Operating Principles

  1. Define completion criteria before execution.
  2. Decompose work into agent-sized units.
  3. Route model tiers by task complexity.
  4. Measure with evals and regression checks.

Eval-First Loop

  1. Define capability eval and regression eval.
  2. Run baseline and capture failure signatures.
  3. Execute implementation.
  4. Re-run evals and compare deltas.

Example workflow:

1. Write test that captures desired behavior (eval)
2. Run test → capture baseline failures
3. Implement feature
4. Re-run test → verify improvements
5. Check for regressions in other tests

Task Decomposition

Apply the 15-minute unit rule:

  • Each unit should be independently verifiable
  • Each unit should have a single dominant risk
  • Each unit should expose a clear done condition

Good decomposition:

Task: Add user authentication
├─ Unit 1: Add password hashing (15 min, security risk)
├─ Unit 2: Create login endpoint (15 min, API contract risk)
├─ Unit 3: Add session management (15 min, state risk)
└─ Unit 4: Protect routes with middleware (15 min, auth logic risk)

Bad decomposition:

Task: Add user authentication (2 hours, multiple risks)

Model Routing

Choose model tier based on task complexity:

  • Haiku: Classification, boilerplate transforms, narrow edits

    • Example: Rename variable, add type annotation, format code
  • Sonnet: Implementation and refactors

    • Example: Implement feature, refactor module, write tests
  • Opus: Architecture, root-cause analysis, multi-file invariants

    • Example: Design system, debug complex issue, review architecture

Cost discipline: Escalate model tier only when lower tier fails with a clear reasoning gap.

Session Strategy

  • Continue session for closely-coupled units
    • Example: Implementing related functions in same module

Read the full file on GitHub · 136 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. 1mo ago First seen · 136 lines · 40 tokens per session scan A f2d7427f30ae

Subscribe to this mod's changes

agentic-engineering is a skill published in the GitHub repository mit-network/everything-claude-code (88 stars, last pushed 6mo ago), licensed MIT. It adds 40 tokens to every session and 862 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to agentic-engineering, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

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.

microsoft/vscode · 53 tokens