ECC: Instructions file for Kiro

.kiro/steering/git-workflow.md

git-workflow is an instructions file for Kiro from affaan-m/ECC. It costs 233 tokens per session, scanned B, original, MIT.

A set of Git workflow rules for commit messages and pull requests. Git records code changes so teams can work on branches and review changes before merging them.

In plain words
What is it for?
Use it when naming commits, reviewing all changes since a base branch, preparing pull request summaries, documenting test plans, and pushing new branches.
Why use it?
It makes commits easier to understand and helps pull requests describe the complete change, its tests, and the relevant history.

Instructions file for Kiro

Written for Kiro: installed under .kiro/. Also seen: reads .claude/ paths.

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

About the project

ECC is a toolkit that organizes and improves how coding agents work through skills, memory, security checks, research practices, and related extensions. It is for developers using agents such as Claude Code, Codex, OpenCode, and Cursor.

affaan-m/ECC · 287,323 stars · on GitHub · ecc.tools

Reuse

Borrowing it

Nothing to install: this file belongs to affaan-m/ECC. 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/affaan-m/ECC/main/.kiro/steering/git-workflow.md
Clone the repo
git clone --depth 1 https://github.com/affaan-m/ECC

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 git-workflow

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/affaan-m/ecc/git-workflow"><img src="https://agentmods.dev/badge/instructions/affaan-m/ecc/git-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 233 This file is loaded in full into every session.
When invoked 233 The same file — it is already loaded in full.
Security scan B 1 finding. 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.00233 $0.00233
Opus 5.5 $0.00093 $0.00093
Sonnet 5.5 $0.00047 $0.00047
Haiku 4.5 $0.00023 $0.00023

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

Security

Grade B, and why

git-workflow scanned grade B with 1 finding 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 12d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

Note: ECC-managed installs set `"includeCoAuthoredBy": false` in `~/.claude/settings.json`, so commits carry no `Co-Authored-By` trailer by default. To keep Claude attribution, set `"includeCoAuthoredBy": true` or config
.kiro/steering/git-workflow.md · 31 lines

What it actually says

Git Workflow

Commit Message Format

<type>: <description>

<optional body>

Types: feat, fix, refactor, docs, test, chore, perf, ci

Note: ECC-managed installs set "includeCoAuthoredBy": false in ~/.claude/settings.json, so commits carry no Co-Authored-By trailer by default. To keep Claude attribution, set "includeCoAuthoredBy": true or configure attribution; ECC never overwrites an explicit choice.

Pull Request Workflow

When creating PRs:

  1. Analyze full commit history (not just latest commit)
  2. Use git diff [base-branch]...HEAD to see all changes
  3. Draft comprehensive PR summary
  4. Include test plan with TODOs
  5. Push with -u flag if new branch

For the full development process (planning, TDD, code review) before git operations, see the development workflow rule.

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. 12d ago Changed a64109174fd1
  2. 1mo ago First seen · 31 lines · 233 tokens per session scan B 83ceeafc369f

Subscribe to this mod's changes

git-workflow is an instructions file published in the GitHub repository affaan-m/ECC (287,323 stars, last pushed 3d ago), licensed MIT. It adds 233 tokens to every session, about $0.0009 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-07.

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,715 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,581 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

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 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