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/nshkrdotcom/agent_session_manager/agents-mdgit clone --depth 1 https://github.com/nshkrdotcom/agent_session_managerWhat 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.00691 | $0.00691 |
| Opus 5 | $0.00345 | $0.00345 |
| Sonnet 5 | $0.00138 | $0.00138 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
agent_session_manager 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.
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure
lib/contains publicASMmodules and provider/session orchestration internals.test/contains ExUnit coverage and optional SDK stubs.guides/,examples/,README.md, andCHANGELOG.mdmust stay aligned with runtime and dependency behavior.doc/is generated output and should not be edited.
Execution Plane Stack
- ASM sits above
cli_subprocess_coreand provider SDKs; do not expose rawExecutionPlane.*transport internals as public API. - Use
CliSubprocessCorefacades and mapped ASM envelopes for execution surfaces, transport errors, recovery, and events. - Dependency source selection is handled by
build_support/dependency_sources.exsandbuild_support/dependency_sources.config.exs; local overrides use.dependency_sources.local.exs. - Keep
cli_subprocess_coredependency resolution publish-aware: local path deps for sibling development, GitHub fallback for clean clones, and Hex constraints for release builds. - Dependency source selection must not use environment variables.
- This repo is not a Weld consumer in this pass and must not receive a blind Weld dependency. Weld verification is limited to discovered Weld consumers.
- Runtime application code under
lib/**must not call direct OS env APIs such asSystem.get_env,System.fetch_env,System.put_env, orSystem.delete_env. - Runtime and deployment env reads belong in
config/runtime.exsor an explicitConfig.Provider; runtime modules read materialized values throughASM.Envor explicit caller options.
Gates
- Run
mix format. - Run
mix compile --warnings-as-errors. - Run
mix test. - Run
mix credo --strict. - Run
mix dialyzer. - Run
mix docs --warnings-as-errors.
Live Provider Checks
For live provider checks, use ~/scripts/with_bash_secrets <command>. It sources
~/.bash/bash_secrets and execs the command. Do not print secret values. Pipe
LINEAR_API_KEY via stdin for Linear examples. GitHub live examples use gh auth
or GH_TOKEN/GITHUB_TOKEN from the wrapper. Codex SDK examples use the existing
Codex/OpenAI machine auth through the wrapper. Live provider smoke is not product
acceptance unless it runs the product-owned Extravaganza command path.
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.
- 2d ago First seen · 59 lines · 691 tokens per session scan A ba56fb76fed8
agent_session_manager AGENTS.md is an instructions file published in the GitHub repository nshkrdotcom/agent_session_manager (11 stars, last pushed 21d ago), licensed MIT. It adds 691 tokens to every session, about $0.0035 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
eliza AGENTS.md
Instructions for elizaOS/eliza, covering elizaos repository guide, how repository instructions work, naming, before editing and toolchain.
LobsterAI AGENTS.md
AGENTS.md instructions for netease-youdao/LobsterAI, covering agents.md, instruction scope, project snapshot, cowork vs openclaw and commands.
better-chatbot AGENTS.md
AGENTS.md instructions for keinsaasforever/better-chatbot, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.
zhin CLAUDE.md
Instructions for zhinjs/zhin, covering claude.md, project overview, commands, bootstrap (first-time or after clean) and single package.
zhin zhin-plugin.instructions.md
Instructions for zhinjs/zhin, covering zhin plugin runtime authoring, package contract, convention directories, imports and native typescript and command routes.
skill-based-architecture AGENTS.md
Instructions for WoJiSama/skill-based-architecture, covering agents.md, quick routing (survives context truncation), auto-triggers and red flags — stop.