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 rules/a-tokyo/aiworkspace/workspacegit clone --depth 1 https://github.com/a-tokyo/aiworkspaceWhat 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.00116 | $0.00116 |
| Opus 5 | $0.00058 | $0.00058 |
| Sonnet 5 | $0.00023 | $0.00023 |
| Haiku 4.5 | $0.00012 | $0.00012 |
Grade A, and why
workspace 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.
What it actually says
- Open the parent workspace root (e.g.
~/dev/<your-org>/) when working across repos. - Prefer the nearest
AGENTS.mdand.agents/skills/to the code being changed. - Workspace-wide MCP and agent configs live in
<workspace-repo>/root-config/and mirror to the parent root onnpm run sync. - Disable optional MCP servers you do not use in your editor Settings — definitions stay team-shared in
.agents/mcp.json.
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.
- 2d ago First seen · 9 lines · 116 tokens per session scan A d6bfd6f6a79d
workspace is a cursor rule published in the GitHub repository a-tokyo/aiworkspace (19 stars, last pushed 14d ago), licensed Apache-2.0. It adds 116 tokens to every session, about $0.0006 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 cursor rules, from other repositories
020-agent-skill-authoring
Authoring agent, skill, and command markdown for cross-harness portability.
000-project-conventions
This is a multi-harness plugin marketplace. Source lives under plugins/; per-harness artifacts (.codex/, .cursor-plugin/, .opencode/, commands/) are generated.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.