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/fodyz/yangmap/agents-mdgit clone --depth 1 https://github.com/FODYZ/yangmapWhat 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.00622 | $0.00622 |
| Opus 5 | $0.00311 | $0.00311 |
| Sonnet 5 | $0.00124 | $0.00124 |
| Haiku 4.5 | $0.00062 | $0.00062 |
Grade A, and why
yangmap 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 yesterday.
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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project agent memory
This file is the project's committed home for project-intrinsic agent knowledge: build, test, release, architecture, and sharp-edge notes that should travel with the code.
- Add durable project-specific notes here as they are discovered through real work.
Naming: English prose, French API surface
The repo was translated to English prose in 2026-08 (README, docs, docstrings,
comments, CLI help, MCP tool descriptions), but the actual API surface was
deliberately left in French: the CLI subcommands chercher/detail, the
MCP tool names yang_chercher/yang_detail, the Python method names
(Carte.chercher, search.chercher), and every JSON/dict field returned to
callers (plateforme, chemin, bundle_servi, version_demandee, ecart,
avertissement, resultats, cles, cles_a_fournir, noeud, enfants,
action_requise). Do not rename these without checking for external
consumers first — docs/VALIDATION-2026-08-10.md documents a real one
(netlive) already calling yang_chercher/yang_detail by name. Renaming
the tool/CLI surface is a breaking API change, not a translation.
Also deliberately untranslated: goldenset/golden.yaml's question: values
and the French test queries scattered in tests/test_integration_netlive.py
and tests/test_search.py — these exercise the French→English lexicon in
yangmap/search.py::LEXIQUE, which is real functionality (users query in
French, vendor YANG descriptions are in English), not leftover prose.
Tests that pytest.raises(..., match="...") or assert on substrings of
runtime messages are coupled to the (now English) error/print text in
yangmap/*.py. If you change a user-facing message, grep the test suite for
the old substring before assuming the tests still pass.
Build/test
pip install -e ".[dev]" then pytest -m "not lab" (91 tests, offline).
pytest -m build needs pyang (in the dev/build extras) plus a real
downloaded bundle under ~/.yangmap to do anything beyond the 3 synthetic
tests. pytest -m lab needs a real containerlab and netlive installed —
see tests/test_integration_netlive.py's module docstring for the env vars.
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.
- yesterday First seen · 46 lines · 622 tokens per session scan A 741f02309822
yangmap AGENTS.md is an instructions file published in the GitHub repository FODYZ/yangmap (0 stars, last pushed 3d ago), licensed MIT. It adds 622 tokens to every session, about $0.0031 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.