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.
npx agentmods add instructions/mrgnhnt96/sip/agents-mdgit clone --depth 1 https://github.com/mrgnhnt96/sipWrote 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/mrgnhnt96/sip/agents-md)<a href="https://agentmods.dev/instructions/mrgnhnt96/sip/agents-md"><img src="https://agentmods.dev/badge/instructions/mrgnhnt96/sip/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 | $0.02533 | $0.02533 |
| Opus 5 | $0.01267 | $0.01267 |
| Sonnet 5 | $0.00507 | $0.00507 |
| Haiku 4.5 | $0.00253 | $0.00253 |
Grade A, and why
sip 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.
How it starts
The opening of the file, as written. The whole thing — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sip — agent & contributor guide
sip_cli is a single Dart package (no mono-repo, no codegen). It publishes one
executable, sip.
Quick loops
| Goal | Command |
|---|---|
| Run the test suite | dart test |
| One file | dart test test/src/domain/args_test.dart |
| Analyze | dart analyze . --fatal-infos --fatal-warnings |
| Format | dart format . |
| Try a change end-to-end | dart compile exe bin/sip.dart -o /tmp/sip_dev then run /tmp/sip_dev |
dart testis still the reference.sip testused to report a passing run for a failing suite; it now counts failures correctly and also fails on a non-zero exit code from the test process, so a failure the parser misses can no longer pass silently. It remains a layer of parsing overdart test, so when a result looks surprising, confirm withdart testdirectly.
To exercise the CLI without touching a globally activated sip, compile to a
scratch path and run that binary. sip run install (alias sip run i)
overwrites your global install with the working tree, which is convenient but
not reversible in one step.
CI
.github/workflows/ci.yml runs on ubuntu and windows: dart analyze --fatal-infos --fatal-warnings, dart test, then a shell smoke test in
test/integration/smoke against sip activated from source. Every step tees to
ci_logs/, which is uploaded as an artifact.
hooks/pre_commit.dart (hooksman) formats and analyzes staged Dart files with
--fatal-infos --fatal-warnings on commit.
Project layout
bin/sip.dart entrypoint
lib/sip_runner.dart top-level arg dispatch (the command table lives here)
lib/src/commands/ one directory or file per command
lib/src/commands/mcp/ the `sip mcp` server and its tools
lib/src/deps/ scoped_deps providers — the injection seam
lib/src/domain/ models: Script, ScriptsConfig, Args, TestData, ...
lib/src/utils/ constants, mixins, helpers
test/src/ unit tests
test/e2e/ per-feature dirs with an `inputs/scripts.yaml`
test/integration/smoke/ the only thing CI actually runs
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.
- 4d ago First seen · 204 lines · 2,533 tokens per session scan A 8aae1dd05403
sip AGENTS.md is an instructions file published in the GitHub repository mrgnhnt96/sip (5 stars, last pushed 14d ago), licensed MIT. It adds 2,533 tokens to every session, about $0.0127 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.
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).
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.
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.
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.
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).
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.