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/swarmauri/swarmauri-sdk/agents-mdgit clone --depth 1 https://github.com/swarmauri/swarmauri-sdkWrote 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/swarmauri/swarmauri-sdk/agents-md)<a href="https://agentmods.dev/instructions/swarmauri/swarmauri-sdk/agents-md"><img src="https://agentmods.dev/badge/instructions/swarmauri/swarmauri-sdk/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.00537 | $0.00537 |
| Opus 5 | $0.00269 | $0.00269 |
| Sonnet 5 | $0.00107 | $0.00107 |
| Haiku 4.5 | $0.00054 | $0.00054 |
Grade A, and why
swarmauri-sdk 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contribution Guide
Follow these high-level steps when updating this repository:
- Style and Linting – run
uv run --directory <member> --package <name> ruff format .followed byruff check . --fixinside each changed package underpkgs/. - Tests – execute tests in isolation from
pkgs/withuv run --package <name> --directory <member> pytest. - Documentation and Style – keep code consistent with STYLE_GUIDE.md.
- Pull Requests – ensure commits are well described and reference related issues if applicable.
- Default Branch – the repository's default branch is
master.
Changes to the peagen package require additional validation steps detailed in
pkgs/standards/peagen/AGENTS.md. Plugins should be instantiated directly;
avoid using the PluginManager unless explicitly directed otherwise.
Swarmauri & Tigrbl Package Requirements
- All Swarmauri packages must include the Swarmauri SVG branding in their
README.md, the completed badge set (downloads, hits, supported Python versions, license, and release version), a dedicated Features section, installation instructions for bothuvandpip, and usage guidance that explains the expected workflows. pyproject.tomlentries for new Swarmauri packages must specify the planning development-stage classifier, a descriptive summary, detailed keywords, and list Jacob Stewart<[email protected]>as an author (do not add the Swarmauri organization as a separate author entry).- Package metadata and documentation must communicate support for Python 3.10 through 3.12, and classifiers should be added accordingly.
- When working on Tigrbl packages the same rules apply, but swap the branding image with the Tigrbl SVG theme.
- Branding asset locations:
- Swarmauri theme SVG:
https://github.com/swarmauri/swarmauri-sdk/blob/3d4d1cfa949399d7019ae9d8f296afba773dfb7f/assets/swarmauri.brand.theme.svg - Tigrbl theme SVG:
https://github.com/swarmauri/swarmauri-sdk/blob/a170683ecda8ca1c4f912c966d4499649ffb8224/assets/tigrbl.brand.theme.svg
- Swarmauri theme SVG:
- If you are unsure which branding to use, default to the Swarmauri SVG.
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 · 37 lines · 537 tokens per session scan A 1f9e0e817272
swarmauri-sdk AGENTS.md is an instructions file published in the GitHub repository swarmauri/swarmauri-sdk (103 stars, last pushed 22d ago), licensed Apache-2.0. It adds 537 tokens to every session, about $0.0027 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
agent-framework copilot-instructions.md
Instructions for microsoft/agent-framework, covering github copilot instructions, repository structure and architectural decision records (adrs).
agent-framework python.instructions.md
Instructions for microsoft/agent-framework: See AGENTS.md for project structure and package documentation. Detailed conventions are in the agent skills under .github/skills/.
jido AGENTS.md
AGENTS.md instructions for agentjido/jido, covering agents.md - jido guide, intent, runtime baseline, commands and architecture snapshot.
swarmclaw CLAUDE.md
Instructions for swarmclawai/swarmclaw, covering claude.md, keeping instructions in sync, dev server, code quality and architecture.
squads-cli AGENTS.md
Instructions for agents-squads/squads-cli, covering agent instructions, specs — read before non-trivial changes, what this is, repository structure and build and test.
squads-cli CLAUDE.md
Instructions for agents-squads/squads-cli: All agent instructions live in AGENTS.md (the vendor-neutral standard) so Claude, Codex, Gemini, and Cursor read the same guidance.