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/changexbc/workbuddy-switch/agents-mdgit clone --depth 1 https://github.com/changexbc/workbuddy-switchWrote 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/changexbc/workbuddy-switch/agents-md)<a href="https://agentmods.dev/instructions/changexbc/workbuddy-switch/agents-md"><img src="https://agentmods.dev/badge/instructions/changexbc/workbuddy-switch/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.00440 | $0.00440 |
| Opus 5 | $0.00220 | $0.00220 |
| Sonnet 5 | $0.00088 | $0.00088 |
| Haiku 4.5 | $0.00044 | $0.00044 |
Grade A, and why
workbuddy-switch 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 today.
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 — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trellis Instructions
These instructions are for AI assistants working in this project.
This project is managed by Trellis. The working knowledge you need lives under .trellis/:
.trellis/workflow.md— development phases, when to create tasks, skill routing.trellis/spec/— package- and layer-scoped coding guidelines (read before writing code in a given layer).trellis/workspace/— per-developer journals and session traces.trellis/tasks/— active and archived tasks (PRDs, research, jsonl context)
If a Trellis command is available on your platform (e.g. /trellis:finish-work, /trellis:continue), prefer it over manual steps. Not every platform exposes every command.
If you're using Codex or another agent-capable tool, additional project-scoped helpers may live in:
.agents/skills/— reusable Trellis skills.codex/agents/— optional custom subagents
Managed by Trellis. Edits outside this block are preserved; edits inside may be overwritten by a future trellis update.
UI Component Policy
- For frontend UI, prefer the project's existing shadcn components and compose them before writing custom interactive primitives.
- If a required component is missing, add the matching shadcn/Radix component and wrap it under
src/components/ui/so styling, accessibility, focus management, and behavior stay consistent. - Write a custom component only when shadcn components and their composition APIs cannot satisfy the requirement. Record the reason before doing so.
- Custom UI must still reuse the project's Rhea theme tokens, spacing, radii, states, and accessibility conventions. Do not substitute native interactive shortcuts such as
details/summarywhen an appropriate shadcn component exists.
Git Commit Language
- Use Conventional Commit type prefixes such as
feat:,fix:, anddocs:. - Write the commit subject and body in Chinese by default. Use English only when the user explicitly requests it.
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.
- today First seen · 34 lines · 440 tokens per session scan A ca0f7a66fa93
workbuddy-switch AGENTS.md is an instructions file published in the GitHub repository changexbc/workbuddy-switch (129 stars, last pushed 2d ago), licensed MIT. It adds 440 tokens to every session, about $0.0022 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-09-03.
Other instructions, from other repositories
anarlog AGENTS.md
AGENTS.md instructions for fastrepl/anarlog, covering commands, pre-commit verification, guidelines, code style and cli tui command architecture.
terax-ai AGENTS.md
AGENTS.md instructions for crynta/terax-ai, a project described as: Lightweight (7MB) Terminal-first AI-native dev workspace.
phase CLAUDE.md
Claude Code instructions for phase-rs/phase, covering claude.md, project overview, design principles — read this first, when in doubt and agent team orchestration standards.
asyar AGENTS.md
AGENTS.md instructions for Xoshbin/asyar, covering asyar project agent guidelines & rules, 1. strict git policy (no git writes without asking), 2. no ai attribution, 3. mandatory verification & local ci matrix and 4. formatting enforcement.
anarlog CLAUDE.md
Claude Code instructions for fastrepl/anarlog, a project described as: Open source Granola AI Alternative.
terax-ai CLAUDE.md
Claude Code instructions for crynta/terax-ai, a project described as: Lightweight (7MB) Terminal-first AI-native dev workspace.