agentmods.dev

toolmux AGENTS.md

Repository instructions for coding agents working on Toolmux, a tool that connects agents with providers, tools, workflows, and other services.

In plain words
What is it for?
Use it when changing Toolmux commands, providers, authentication, policies, supported tools, workflows, tests, releases, or documentation.
Why use it?
It keeps agent guidance, user documentation, contributor instructions, and release or security requirements consistent as the project changes.

Instructions file for CodexOpenCode

2 28d ago A scan 7,455 tokens original MIT
View the source file fiam/toolmux
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/fiam/toolmux/agents-md
Clone the repo
git clone --depth 1 https://github.com/fiam/toolmux

Made for: Codex, OpenCode.

Per session 7,455 This file is loaded in full into every session.
When invoked 7,455 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.07455 $0.07455
Opus 5 $0.03728 $0.03728
Sonnet 5 $0.01491 $0.01491
Haiku 4.5 $0.00745 $0.00745

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

Security

Grade A, and why

toolmux 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 · 624 lines

How it starts

The opening of the file, as written. The whole thing — 624 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

This file defines repository expectations for coding agents working on Toolmux. Keep it current whenever build, test, style, security, release, or workflow requirements change.

Maintenance

Agents must update this file when they:

  1. Change the supported Go version or toolchain setup.
  2. Add, remove, or rename important make targets or CI checks.
  3. Add a new provider, auth mode, policy behavior, or test class.
  4. Add, remove, rename, or change a supported native toolbox, remote MCP catalog entry, workflow template, or supported agent.
  5. Change commit, release, linting, formatting, or security expectations.
  6. Change the public OSS/private infrastructure repository boundary.
  7. Change CLI output behavior, terminal UX, or machine-readable schemas.
  8. Change public user behavior that should be reflected in README.md.
  9. Change developer workflow that should be reflected in CONTRIBUTING.md.

Agents must keep README.md, CONTRIBUTING.md, and this file in sync:

  1. README.md is for users. Update it for user-visible commands, provider status, supported toolboxes and tools, workflow templates, supported agents, auth flows, output modes, install instructions, and safety notes.
  2. CONTRIBUTING.md is for developers. Update it for local setup, test/lint workflow, provider integration rules, PR expectations, and release tooling.
  3. AGENTS.md is for coding agents. Update it for repository expectations that agents must follow while editing code or docs.
  4. Do not add or rename commands, flags, providers, auth behavior, policy behavior, or quality gates without checking whether all three docs need an update.

When updating Go guidance, check the official Go release notes and release history first:

  1. https://go.dev/doc/go1.26
  2. https://go.dev/doc/devel/release

Go Version

Use the latest stable Go toolchain. As of 2026-08-04, govulncheck requires Go 1.26.5 as the security-fix patch release for the Go 1.26 line.

Repository expectations:

Read the full file on GitHub · 624 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 · 624 lines · 7,455 tokens per session scan A 747915e23001

Subscribe to this mod's changes

toolmux AGENTS.md is an instructions file published in the GitHub repository fiam/toolmux (2 stars, last pushed 28d ago), licensed MIT. It adds 7,455 tokens to every session, about $0.0373 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.

Data and AITestingWriting and docsai-agentsclicredential-managementdeveloper-toolsgo
Related

Other instructions, from other repositories

warden AGENTS.md

Instructions for stephnangue/warden, covering warden — agent guide, where to start, the agent loop, provider skills and adding a skill for a new provider.

stephnangue/warden · 1,063 tokens

ollama CLAUDE.md

Claude Code instructions for ollama/ollama: See AGENTS.md for the shared agent instructions for this repository.

ollama/ollama · 21 tokens

sq AGENTS.md

Instructions for neilotoole/sq, covering agents.md, about sq, key documents, common commands and conventions.

neilotoole/sq · 3,837 tokens

azure-sdk-for-go go-examples.instructions.md

Instructions for Azure/azure-sdk-for-go, a project described as: This repository is for active development of the Azure SDK for Go. For consumers of the SDK we recommend visiting our public developer docs at.

Azure/azure-sdk-for-go · 113 tokens

cli AGENTS.md

Instructions for planetscale/cli, covering planetscale cli — agent guide, public repository safety, concepts, flag placement and correct.

planetscale/cli · 9,971 tokens

azure-sdk-for-go go-code.instructions.md

Instructions for Azure/azure-sdk-for-go: All code should follow the guidelines from the Azure Go SDK Guidelines. This document is a summary of the most important guidelines to follow when contributing to the Azure Go SDK.

Azure/azure-sdk-for-go · 755 tokens