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/whiletrueblackobelizk/shared-workspace-mcp/agents-mdgit clone --depth 1 https://github.com/WhileTrueBlackObelizk/shared-workspace-mcpWrote 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/whiletrueblackobelizk/shared-workspace-mcp/agents-md)<a href="https://agentmods.dev/instructions/whiletrueblackobelizk/shared-workspace-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/whiletrueblackobelizk/shared-workspace-mcp/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.1 | $0.00931 | $0.00931 |
| Opus 5 | $0.00465 | $0.00465 |
| Sonnet 5 | $0.00186 | $0.00186 |
| Haiku 4.5 | $0.00093 | $0.00093 |
Grade A, and why
shared-workspace-mcp 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 5d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions
Source of truth for how agents work in this repo. Two parts: an operating contract (portable — copy to any project) and this repo (specifics). Keep everything ponytail-small.
Operating contract (portable)
Decide vs. ask
Default to deciding. Only stop and ask for the rows on the right. If a question has an obvious default, take it and say so in one line — don't block on it.
| Decide yourself (no question) | Ask first |
|---|---|
| Naming, layout, formatting that match existing patterns | Adding a new dependency |
| Which stdlib / already-installed dep to use (ponytail ladder) | Breaking a tool contract or storage schema |
| Writing the smallest test / self-check for new logic | Deleting data or files; anything irreversible |
| Reading, searching, running checks and gates | Security-relevant change (auth, network exposure, secrets) |
| Commit to a branch, open a PR, update required docs | Acceptance criteria genuinely ambiguous and undefaultable |
Autonomy levels
How much the agent does unattended. The gates enforce it; this just names the setting. Default: L2.
| Level | The agent may, unattended | Stops for sign-off at |
|---|---|---|
| L0 suggest | Read, search, propose — change nothing | any write |
| L1 branch | Edit, run checks/gates, commit to a branch, open a PR | merge / push to main |
| L2 ship | L1 + merge/push to main once all hard gates pass |
the "ask first" rows below |
| L3 unattended | L2 + act on schedules (dependency triage, nightly drift) without a prompt | same |
No level ever skips the "Ask first" column (new dep, schema/contract break, delete, deploy, security/network). Those always need a human.
Workflow: gated by default
Run real work through the pipeline gates instead of self-declaring done:
- intake —
learning_searchthe task first, so past mistakes aren't repeated. - plan — pre-register
acceptance_criteria(the definition of done). - implement — the smallest diff that works.
- test —
run_check; evidence must postdate your last edit (freshness). - review —
verify_file_refsfor any file:line claim you make. - handover —
context_snapshot/handover_prepare: outcome, next steps, risks.
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.
- 5d ago First seen · 74 lines · 931 tokens per session scan A 14a2f734d5ce
shared-workspace-mcp AGENTS.md is an instructions file published in the GitHub repository WhileTrueBlackObelizk/shared-workspace-mcp (0 stars, last pushed 24d ago), licensed MIT. It adds 931 tokens to every session, about $0.0047 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.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.