M3E: Instructions file for Kiro

.kiro/steering/structure.md

M3E structure.md is an instructions file for Kiro from akaghef/M3E. It costs 828 tokens per session, scanned A, original, MIT.

Project-structure instructions for the M3E codebase. They explain where active source code, stable releases, documents, protocols, and agent skills belong.

In plain words
What is it for?
Use them when adding or updating M3E code, specifications, operational protocols, or project-local agent instructions.
Why use it?
They reduce confusion about which directory owns a change and help prevent new work from being placed in the wrong part of the repository.

Instructions file for Kiro

Written for Kiro: installed under .kiro/. Also seen: mentions Codex.

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

View source ↗ akaghef/M3E
Reuse

Borrowing it

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

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 M3E structure.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/akaghef/m3e/structure"><img src="https://agentmods.dev/badge/instructions/akaghef/m3e/structure.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 828 This file is loaded in full into every session.
When invoked 828 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 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.00828 $0.00828
Opus 5.5 $0.00331 $0.00331
Sonnet 5.5 $0.00166 $0.00166
Haiku 4.5 $0.00083 $0.00083

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

Security

Grade A, and why

M3E structure.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 5d 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.

.kiro/steering/structure.md · 109 lines

How it starts

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

Project Structure

Organization Philosophy

M3E separates product source, stable release output, strategy/spec documents, operations rules, protocols, and task artifacts. New work should land in the smallest directory boundary that already owns the behavior.

Directory Patterns

Active Product Source

Location: beta/

Active development target. Contains TypeScript source, prompts, tests, build config, local server, browser viewer, and beta-specific policy.

Stable Release Surface

Location: final/

Stable distribution target. Do not implement new product behavior directly here; validated beta changes are migrated into final.

Product and Architecture Documents

Location: docs/

Long-lived planning, specification, architecture, operations, ADR, task, and daily documents. Design/spec/architecture prose is Japanese by default.

Runtime Protocols

Location: docs/protocols/

Operational protocols for worker behavior, map writes, scope operations, handoff packets, and map-manager routing.

Agent Skills

Location: .agents/skills/

Project-local skill instructions for M3E map, map manager, worker, notation, and bridge tasks. Do not duplicate detailed behavior elsewhere when a local skill is the route.

Scripts

Location: scripts/

Operational helpers, launch scripts, worktree lifecycle helpers, and platform-specific runtime setup.

Backlog and Ideas

Location: backlog/, docs/ideas/

backlog/ is the inbox for unclassified captures and pending material; docs/ideas/ is the canonical home for classified ideas. Promote stable decisions into docs/06_Operations/Decision_Pool.md, docs/03_Spec/, docs/04_Architecture/, or ADRs as appropriate.

Beta Source Patterns

Shared Types

Location: beta/src/shared/

Shared TypeScript contracts used across Node and browser code.

Node Runtime

Location: beta/src/node/

Local server, SQLite persistence, sync/import/export, AI proxy, audit, backup, graph runtime, and CLI utilities.

Read the full file on GitHub · 109 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. 5d ago First seen · 109 lines · 828 tokens per session scan A 03697f5a2ae1

Subscribe to this mod's changes

M3E structure.md is an instructions file published in the GitHub repository akaghef/M3E (11 stars, last pushed 5d ago), licensed MIT. It adds 828 tokens to every session, about $0.0033 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-10-02.

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 · 6,805 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,680 tokens

generative-ai-for-beginners AGENTS.md

AGENTS.md instructions for microsoft/generative-ai-for-beginners, covering agents.md, project overview, setup commands, initial repository setup and clone the repository.

microsoft/generative-ai-for-beginners · 2,850 tokens