What is SwarmAI swarmai-dev-rules.md?

A set of project-specific development instructions for SwarmAI, including platform rules, naming conventions, build commands, tests, and checks required before pushing code. It also explains which repository rules take priority.

Use it to follow the repository's build, test, evaluation, commit, and push procedures while developing SwarmAI.

It helps prevent unsafe or invalid changes from being pushed by making the project's required checks and workflow explicit.

How xg-gh-25/SwarmAI configures Kiro

Reuse

Borrowing it

Nothing to install: this file belongs to xg-gh-25/SwarmAI. 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/xg-gh-25/SwarmAI/main/.kiro/steering/swarmai-dev-rules.md

Clone the repo

git clone --depth 1 https://github.com/xg-gh-25/SwarmAI

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/xg-gh-25/swarmai/swarmai-dev-rules/github.svg)](https://agentmods.dev/instructions/xg-gh-25/swarmai/swarmai-dev-rules)

Your own site

<a href="https://agentmods.dev/instructions/xg-gh-25/swarmai/swarmai-dev-rules"><img src="https://agentmods.dev/badge/instructions/xg-gh-25/swarmai/swarmai-dev-rules/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/instructions/xg-gh-25/swarmai/swarmai-dev-rules"><img src="https://agentmods.dev/badge/instructions/xg-gh-25/swarmai/swarmai-dev-rules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,677 This file is loaded in full into every session.

When invoked 1,677 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.

Model	Per session	Once invoked
Fable 5.1	$0.01677	$0.01677
Opus 5	$0.00839	$0.00839
Sonnet 5	$0.00335	$0.00335
Haiku 4.5	$0.00168	$0.00168

Measured 2d ago against content hash 25d32c0ba6d8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

SwarmAI swarmai-dev-rules.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 2d 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/swarmai-dev-rules.md · 127 lines

How it starts

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

SwarmAI Development Rules

Rules for writing code in this project. For architecture overview, see AGENTS.md.

Repo Context & Push Gate (authoritative — overrides global steering)

This is a PERSONAL GitHub project, NOT an Amazon Brazil/internal repo. The global amazon-builder/* steering (Brazil, CRUX, Coral, Taskei, "never push", internal production-safety) DOES NOT APPLY here. Workspace rules win on conflict.

git push origin main is the NORMAL workflow (commit to main directly — no branches, no PRs). But push is GATED by agent quality assurance:

MUST NOT push to GitHub unless ALL of these passed locally for the change:

Build green — backend ./prod.sh build, and/or cd desktop && npm run build:all (whichever the change touches).
Tests green — at least the affected suites (python -m pytest tests/test_<module>.py / cd desktop && npm test -- --run); full suite when the blast radius warrants.
Eval green — cd backend && python scripts/ci_eval_gate.py.

If any of build / tests / eval was not run or is failing → DO NOT push. Never tag on red CI. This local gate is the prerequisite for agent quality; pushing unbuilt/untested/un-evaluated code defeats it.

Platform Rules

Port 18321 is FIXED (no portpicker, no dynamic allocation). Dev uses 8000.
No import fcntl at module top level — use from utils.file_lock import flock_exclusive
No lsof in scripts — use nc -z 127.0.0.1 PORT (lsof hangs on macOS)
/shutdown returns 403 in daemon/hive mode — never kill background services via API
Channels (Slack) only run in daemon/hive mode — mode guard in main.py

API Naming Convention

Backend: snake_case (Python/Pydantic)
Frontend: camelCase (TypeScript)
ALWAYS update toCamelCase() functions in desktop/src/services/*.ts when adding fields

Development Commands

./dev.sh                        # Full dev: backend (port 8000) + frontend + Tauri
./dev.sh backend                # Backend only
./prod.sh build                 # PyInstaller + verify + deploy to daemon
./prod.sh release               # Full release cycle
./prod.sh status                # Daemon health + versions
cd desktop && npm run build:all # Frontend production build

Read the full file on GitHub · 127 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.

2d ago First seen · 127 lines · 1,677 tokens per session scan A 25d32c0ba6d8

Subscribe to this mod's changes

SwarmAI swarmai-dev-rules.md is an instructions file published in the GitHub repository xg-gh-25/SwarmAI (44 stars, last pushed yesterday), licensed MIT. It adds 1,677 tokens to every session, about $0.0084 per session on Opus 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-06.

Commits Git and workflow Testing agentic-ai ai-agent aws-bedrock claude claude-sdk context-engineering

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,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

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

SwarmAI: Instructions file for Kiro