agent_session_manager AGENTS.md

Repository-specific instructions for the agent_session_manager project, a software library that coordinates command execution and provider sessions. They describe its folders, execution layers, dependency sources, and required documentation alignment.

In plain words
What is it for?
Use them when modifying, testing, documenting, or resolving dependencies in the agent_session_manager repository.
Why use it?
They reduce the chance of exposing internal interfaces, choosing the wrong dependency source, or making changes that conflict with the project's architecture. They also clarify which generated files and dependencies should not be changed.

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

Made for: Codex, OpenCode.

Per session 691 This file is loaded in full into every session.
When invoked 691 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.00691 $0.00691
Opus 5 $0.00345 $0.00345
Sonnet 5 $0.00138 $0.00138
Haiku 4.5 $0.00069 $0.00069

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

Security

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.

AGENTS.md · 59 lines

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 public ASM modules and provider/session orchestration internals.
  • test/ contains ExUnit coverage and optional SDK stubs.
  • guides/, examples/, README.md, and CHANGELOG.md must stay aligned with runtime and dependency behavior.
  • doc/ is generated output and should not be edited.

Execution Plane Stack

  • ASM sits above cli_subprocess_core and provider SDKs; do not expose raw ExecutionPlane.* transport internals as public API.
  • Use CliSubprocessCore facades and mapped ASM envelopes for execution surfaces, transport errors, recovery, and events.
  • Dependency source selection is handled by build_support/dependency_sources.exs and build_support/dependency_sources.config.exs; local overrides use .dependency_sources.local.exs.
  • Keep cli_subprocess_core dependency 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 as System.get_env, System.fetch_env, System.put_env, or System.delete_env.
  • Runtime and deployment env reads belong in config/runtime.exs or an explicit Config.Provider; runtime modules read materialized values through ASM.Env or 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.

Read the full file on GitHub · 59 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. 2d ago First seen · 59 lines · 691 tokens per session scan A ba56fb76fed8

Subscribe to this mod's changes

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.