EGC: Instructions file for Kiro

.kiro/steering/dev-mode.md

EGC dev-mode.md is an instructions file for Kiro from Fmarzochi/EGC. It costs 220 tokens per session, scanned A, a copy of ECC dev-mode.md, Apache-2.0.

A development workflow for implementing features with small, tested steps and readable code. It can use TDD, which means writing tests before the code they check.

In plain words
What is it for?
Use it while writing or changing code, especially when adding unit tests, implementing a feature incrementally, and checking that the test suite passes.
Why use it?
It gives coding work a repeatable sequence and calls attention to edge cases, errors, secrets, and project standards. Frequent tests help catch mistakes during implementation.

Instructions file for Kiro

Written for Kiro: installed under .kiro/.

This is Fmarzochi/EGC's own configuration. It tells Kiro how to work on EGC 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 EGC configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Fmarzochi/EGC. 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/Fmarzochi/EGC/main/.kiro/steering/dev-mode.md
Clone the repo
git clone --depth 1 https://github.com/Fmarzochi/EGC

Made for: Kiro.

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 EGC dev-mode.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/fmarzochi/egc/dev-mode/github.svg)](https://agentmods.dev/instructions/fmarzochi/egc/dev-mode)
Your own site
<a href="https://agentmods.dev/instructions/fmarzochi/egc/dev-mode"><img src="https://agentmods.dev/badge/instructions/fmarzochi/egc/dev-mode/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 EGC dev-mode.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/fmarzochi/egc/dev-mode"><img src="https://agentmods.dev/badge/instructions/fmarzochi/egc/dev-mode.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 220 This file is loaded in full into every session.
When invoked 220 The same file — it is already loaded in full.
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.00220 $0.00220
Opus 5.5 $0.00088 $0.00088
Sonnet 5.5 $0.00044 $0.00044
Haiku 4.5 $0.00022 $0.00022

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

Security

Grade A, and why

EGC dev-mode.md 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 ECC dev-mode.md — 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/steering/dev-mode.md · 45 lines

What it actually says

Development Mode

Use this context when actively implementing features or writing code.

Focus Areas

  • Write clean, maintainable code
  • Follow TDD workflow when appropriate
  • Implement incrementally with frequent testing
  • Consider edge cases and error handling
  • Document complex logic inline

Workflow

  1. Understand requirements thoroughly
  2. Plan implementation approach
  3. Write tests first (when using TDD)
  4. Implement minimal working solution
  5. Refactor for clarity and maintainability
  6. Verify all tests pass

Code Quality

  • Prioritize readability over cleverness
  • Keep functions small and focused
  • Use meaningful variable and function names
  • Add comments for non-obvious logic
  • Follow project coding standards

Testing

  • Write unit tests for business logic
  • Test edge cases and error conditions
  • Ensure tests are fast and reliable
  • Use descriptive test names

Invocation

Use #dev-mode to activate this context when starting development work.

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 · 45 lines · 220 tokens per session scan A 0bec51fd2cc6

Subscribe to this mod's changes

EGC dev-mode.md is an instructions file published in the GitHub repository Fmarzochi/EGC (67 stars, last pushed today), licensed Apache-2.0. It adds 220 tokens to every session, about $0.0009 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to ECC dev-mode.md, differing in 0 lines, and is treated as a copy.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,649 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,384 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens