archsmith AGENTS.md

A set of repository instructions for coding assistants working on ArchSmith. ArchSmith turns validated JSON diagram data into SVG diagrams, and the instructions describe its packages, dependencies, build process, and contribution rules.

In plain words
What is it for?
Use it when developing or reviewing ArchSmith's renderer, command-line tool, MCP server, schema package, documentation, or related workflows.
Why use it?
It gives assistants the project context and constraints they need before changing code or running tests.

Instructions file for CodexOpenCode

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/ayeshlk/archsmith/agents-md
Clone the repo
git clone --depth 1 https://github.com/ayeshLK/archsmith

Made for: Codex, OpenCode.

Per session 9,374 This file is loaded in full into every session.
When invoked 9,374 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.09374 $0.09374
Opus 5 $0.04687 $0.04687
Sonnet 5 $0.01875 $0.01875
Haiku 4.5 $0.00937 $0.00937

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

Security

Grade A, and why

archsmith AGENTS.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.

AGENTS.md · 183 lines

How it starts

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

AGENTS.md

Guidance for AI coding agents (Claude Code, Cursor, Copilot, Codex, etc.) working on the ArchSmith repository itself.

Scope: this file configures agents contributing to this repo. It complements CONTRIBUTING.md (the human-facing build/governance doc) rather than replacing it — read both, and don't duplicate one into the other if you're updating them.

What this is

A renderer, CLI, and MCP server that turn a validated JSON IR (intermediate representation) into an SVG diagram, in one fixed layered/swimlane house style. See README.md for the full pitch and the IR shape. The short version: @archsmith/renderer is a pure function (IR in, SVG out, no LLM call inside it) — interpretation (sketch/description → IR) is deliberately someone else's job, not this repo's.

Architecture at a glance

npm workspaces monorepo. Four packages, strict one-way dependency chain — each package only knows about the one directly below it:

@archsmith/cli  ─┐
                 ├──▶ @archsmith/renderer ──▶ @archsmith/schema
@archsmith/mcp-server  ─┘
  • packages/schema — the JSON Schema (diagram-schema.json) plus governed registries (registries/{colors,icons,sub-layers}.json). Registry entries are house-style contracts, not per-diagram decisions.
  • packages/renderer — pure function: validated IR in, SVG string out. No I/O beyond reading its own bundled font. No LLM call anywhere inside it. Layout is organized as layout/ (per-column assembly), boxes/ (individual shapes), text/ (font measurement + wrapping via the embedded Arimo font, using fontkit), and svg/ (node model + serialization + font embedding). TypeScript project references (tsc -b) handle inter-package build order — no manual ordering needed.
  • packages/cli — the archsmith binary. Thin commander-based wrapper around render() / validate(). render exits 1 on validation errors, 2 on rendering errors. Also has the author subcommand, an interactive Ink-based wizard — see archsmith author, below.
  • packages/mcp-server — the archsmith-mcp binary. A sibling of the CLI, not a wrapper: calls render() / validate() from @archsmith/renderer directly. server.ts builds the McpServer while index.ts is a thin entrypoint that wires it to StdioServerTransport; the split exists so server.test.ts can connect a real MCP Client over an in-memory transport pair. Never write to stdout — stdout is the JSON-RPC channel and a stray console.log (even for debugging) corrupts the protocol stream. Use console.error for diagnostics.

Read the full file on GitHub · 183 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. 2d ago First seen · 183 lines · 9,374 tokens per session scan A 5c4566ec9b00

Subscribe to this mod's changes

archsmith AGENTS.md is an instructions file published in the GitHub repository ayeshLK/archsmith (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 9,374 tokens to every session, about $0.0469 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-08-31.