magpie AGENTS.md

magpie AGENTS.md is an instructions file for Codex, OpenCode from magpie-lang/magpie. It costs 1,442 tokens per session, scanned A, original, MIT.

Repository instructions for Magpie, a Rust programming-language project with compiler, runtime, tooling, and code-generation components. They describe its workspace structure, build commands, tests, and development conventions.

In plain words
What is it for?
Use them when building Magpie, running workspace or targeted tests, inspecting the compiler pipeline, or changing one of its Rust crates.
Why use it?
They help an agent find the right crate and use the project’s expected Cargo commands, instead of guessing how the multi-part codebase works.

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/magpie-lang/magpie/agents-md
Clone the repo
git clone --depth 1 https://github.com/magpie-lang/magpie

Made for: Codex, OpenCode.

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 magpie AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/magpie-lang/magpie/agents-md.svg)](https://agentmods.dev/instructions/magpie-lang/magpie/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/magpie-lang/magpie/agents-md"><img src="https://agentmods.dev/badge/instructions/magpie-lang/magpie/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 1,442 This file is loaded in full into every session.
When invoked 1,442 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.01442 $0.01442
Opus 5 $0.00721 $0.00721
Sonnet 5 $0.00288 $0.00288
Haiku 4.5 $0.00144 $0.00144

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

Security

Grade A, and why

magpie 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 4d 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 · 93 lines

How it starts

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

Repository Guidelines

Project Structure & Module Organization

Magpie is a Rust workspace (Cargo.toml at repo root) with compiler/tooling crates in crates/. Core flow is split across frontend crates (magpie_lex, magpie_parse, magpie_ast), analysis crates (magpie_sema, magpie_hir, magpie_types, magpie_own), and backend crates (magpie_mpir, magpie_arc, magpie_codegen_llvm, magpie_codegen_wasm). CLI entrypoint is crates/magpie_cli/src/main.rs.
Pipeline orchestration is centered in magpie_driver; runtime and platform/tooling crates (for example magpie_rt, magpie_pkg, magpie_memory, magpie_web, magpie_gpu) are also workspace-critical. Use root Cargo.toml workspace members as the source of truth for full crate inventory.
Language fixtures live in tests/fixtures/*.mp, integration tests in tests/integration_test.rs, and standard library modules in std/std.*/*.mp.

Build, Test, and Development Commands

Use Cargo from repo root:

cargo build -p magpie_cli              # build CLI
cargo build --workspace                # build all crates
cargo run -p magpie_cli -- --help      # inspect CLI
cargo test --workspace                 # full test suite
cargo test --test integration_test     # fixture-driven integration tests
cargo test -p magpie_parse snapshot_hello_parser_output

For CLI usage, global flags must come before subcommands:

cargo run -p magpie_cli -- --entry tests/fixtures/hello.mp --emit mpir,llvm-ir build

Toolchain notes (important for backend/link workflows):

  • lli is needed for common magpie run LLVM-IR execution flow.
  • clang (and often llc) is needed for --emit exe / native linking.
  • Missing native tools usually surface as link diagnostics such as MPLINK01 / MPLINK02.
  • In --llm mode, builds may auto-run formatting unless --no-auto-fmt; expect possible source rewrites when this mode is enabled.

CLI path resolution pitfall:

  • --entry is resolved relative to the current working directory (CWD), not always the repo root.
  • If a command fails to find sources, check CWD first before changing code.

Read the full file on GitHub · 93 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. 4d ago First seen · 93 lines · 1,442 tokens per session scan A a7e7e37b4b5b

Subscribe to this mod's changes

magpie AGENTS.md is an instructions file published in the GitHub repository magpie-lang/magpie (54 stars, last pushed 5mo ago), licensed MIT. It adds 1,442 tokens to every session, about $0.0072 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-30.

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

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 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,182 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,345 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, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

next.js 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