Borrowing it
Nothing to install: this file belongs to creative-int/saya-plugins. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/creative-int/saya-plugins/main/AGENTS.mdgit clone --depth 1 https://github.com/creative-int/saya-pluginsWrote 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/creative-int/saya-plugins/agents-md)<a href="https://agentmods.dev/instructions/creative-int/saya-plugins/agents-md"><img src="https://agentmods.dev/badge/instructions/creative-int/saya-plugins/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/creative-int/saya-plugins/agents-md"><img src="https://agentmods.dev/badge/instructions/creative-int/saya-plugins/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00696 | $0.00696 |
| Opus 5.5 | $0.00278 | $0.00278 |
| Sonnet 5.5 | $0.00139 | $0.00139 |
| Haiku 4.5 | $0.00070 | $0.00070 |
Grade A, and why
saya-plugins 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 27d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Saya plugins — agent guide
Public distribution repo for Saya: generated plugin manifests for Cursor, Codex,
and Claude Code, .mcp.json, MCP Registry server.json, and the secondary
saya-team-brain usage-guide skill. The hero is inbound MCP: external agents
connect to Saya's central remote endpoint to query a team's Saya brain.
The one rule: generate, don't hand-edit
saya.config.ts is the single source of truth. Every manifest, .mcp.json,
server.json, and the README install block are emitted from it by
tooling/generate.ts. Edit the config, then:
pnpm generate # rewrite all generated files
pnpm verify # check:generated + typecheck + build/help + MCP smoke
Never hand-edit the generated files (.mcp.json, .claude-plugin/*,
.codex-plugin/*, .cursor-plugin/*, server.json, the README
AUTO-GENERATED block). CI runs check:generated and fails on drift.
To add a client
Add its install steps to installClients in tooling/generate.ts and, if it
needs a manifest, add the manifest builder to the files map. Regenerate.
Scope
- v0: central remote MCP metadata + 3 client manifests +
.mcp.json+server.json+ one secondary usage-guide skill, generated. - Live origin:
https://mcp.saya.computer/mcp(the custom domain; the older workers.dev origin still answers, but no manifest names it).
Positioning is inbound MCP, not a skill pack. Keep saya-team-brain as usage
guidance; the MCP endpoint is the product surface. Keep readiness claims honest:
mcp.saya.computer/mcp is live and returns real Convex-backed, trust-graded
team knowledge for authenticated workspace members.
CLAUDE.md is a symlink to this file.
Platform posture
tooling — saya plugins repo; no product runtime surface.
Companion plugin profile
This repo intentionally uses the agent-plugin-companion profile rather than
the full app-family turborepo profile. It is a public agent-facing distribution
repo for Saya, so it owns generated plugin manifests, skills, MCP metadata, and
install documentation — not product runtime surfaces.
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.
- 27d ago Changed · -2 lines · -15 tokens per session 8e812666c021
- 2mo ago First seen · 69 lines · 711 tokens per session scan A 42b4552e952b
saya-plugins AGENTS.md is an instructions file published in the GitHub repository creative-int/saya-plugins (0 stars, last pushed 27d ago), licensed MIT. It adds 696 tokens to every session, about $0.0028 per session on Opus 5.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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.