Borrowing it
Nothing to install: this file belongs to Prismer-AI/signet. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Prismer-AI/signet/main/AGENTS.mdgit clone --depth 1 https://github.com/Prismer-AI/signetWrote 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.
[](https://agentmods.dev/instructions/prismer-ai/signet/agents-md)<a href="https://agentmods.dev/instructions/prismer-ai/signet/agents-md"><img src="https://agentmods.dev/badge/instructions/prismer-ai/signet/agents-md.svg" alt="Measured on agentmods" height="20"></a>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.00657 | $0.00657 |
| Opus 5 | $0.00329 | $0.00329 |
| Sonnet 5 | $0.00131 | $0.00131 |
| Haiku 4.5 | $0.00066 | $0.00066 |
Grade A, and why
signet 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 25 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
crates/signet-core/ is the source of truth for signing, verification, delegation, and policy logic. signet-cli/ builds the signet binary. bindings/signet-ts/ produces the WASM layer consumed by packages/signet-core/, while bindings/signet-py/ exposes the Rust core through PyO3 and keeps Python tests in bindings/signet-py/tests/. TypeScript packages live in packages/ (signet-core, signet-mcp, signet-mcp-server, signet-mcp-tools, signet-vercel-ai). Use examples/ for runnable demos and plugins/ for Codex and Claude integrations.
Build, Test, and Development Commands
Use the same commands CI runs:
cargo test --workspaceruns Rust crate and CLI tests.cargo clippy --workspace --all-targets --all-features -- -D warningschecks Rust lint violations.cargo fmt --all -- --checkverifies Rust formatting.wasm-pack build bindings/signet-ts --target nodejs --out-dir ../../packages/signet-core/wasmrebuilds the WASM binding.cd packages/signet-core && npm testruns the TypeScript core build and Node test suite. Repeat in otherpackages/*directories as needed.cd bindings/signet-py && maturin develop && pytest tests/ -vrebuilds and tests the Python binding.npm run version:checkvalidates that all managed package versions match the repo version.
Coding Style & Naming Conventions
Follow existing formatting instead of introducing a new style layer. Rust uses rustfmt defaults, clippy must stay clean, and application crates must remain free of unsafe code. TypeScript is strict (NodeNext, strict: true) and uses ESM. Match existing naming: Rust modules are snake_case, TypeScript source files are lower-case with hyphens only when already established, and tests end with .test.ts or test_*.py. Preserve receipt field names such as params_hash and trace_id; do not rename signed payload fields to camelCase.
Testing Guidelines
Add or update tests with every behavioral change. Keep Rust unit tests close to the module, TypeScript tests under each package’s tests/, and Python coverage under bindings/signet-py/tests/. When changing WASM or cross-language behavior, run both node examples/wasm-roundtrip/test.mjs and the affected package tests.
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.
- 6d ago First seen · 25 lines · 657 tokens per session scan A a41e57f244aa
signet AGENTS.md is an instructions file published in the GitHub repository Prismer-AI/signet (38 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 657 tokens to every session, about $0.0033 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.
Other instructions, from other repositories
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.
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.
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).
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).
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.
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.