Borrowing it
Nothing to install: this file belongs to J-StaR-Films-Studios/VibeCode-Protocol-Suite. 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/J-StaR-Films-Studios/VibeCode-Protocol-Suite/main/AGENTS.mdgit clone --depth 1 https://github.com/J-StaR-Films-Studios/VibeCode-Protocol-SuiteWrote 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/j-star-films-studios/vibecode-protocol-suite/agents-md)<a href="https://agentmods.dev/instructions/j-star-films-studios/vibecode-protocol-suite/agents-md"><img src="https://agentmods.dev/badge/instructions/j-star-films-studios/vibecode-protocol-suite/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.00731 | $0.00731 |
| Opus 5 | $0.00365 | $0.00365 |
| Sonnet 5 | $0.00146 | $0.00146 |
| Haiku 4.5 | $0.00073 | $0.00073 |
Grade A, and why
VibeCode-Protocol-Suite 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 8d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Takomi / VibeCode Protocol Suite Agent Guidelines
This repository provides Takomi CLI, Pi harness extensions, and a curated skills ecosystem (assets/.agent/skills/). Follow these rules when developing, adding, or modifying skills and workflows.
1. Skill Taxonomy & Architecture Rules
To prevent context saturation (prompt bloat) across AI agent harnesses, skills follow the Lean Unified Skills Architecture (docs/features/Lean_Unified_Skills_Architecture.md):
- Add to Existing Umbrella Suites: If a new skill relates to an established domain (testing, Next.js, code intelligence, git operations, agent prompts, UI, office docs, media), add it as a sub-skill inside the relevant suite folder.
- Update Router Context Pointers: When adding a sub-skill, update the parent suite's top-level
SKILL.mdfrontmatterdescriptionto include keyword triggers for the new sub-skill. This enables natural keyword discovery without requiring the user to type the suite name. - When to Create a New Suite: Create a new umbrella suite only when a cluster of 3+ related sub-skills introduces a distinct engineering or creative domain not covered by the existing 12 suites.
- When to Keep a Skill Standalone: Keep a skill standalone at the top level only if it is a single-purpose CLI binary wrapper (e.g.,
audit-website,context7,jules), a global communication mode (e.g.,wait-what,bro,poteto-mode), or an isolated cross-domain utility. - Core Essentials Policy: Never unilaterally add or promote a skill to Core Essentials. The 8 Core Essentials (
takomi,grill-me,code-review,sync-docs,security-audit,agent-recovery,avoid-feature-creep,git-commit-generation) are always active; promotions to Core are decided by the user. - Check for Merges & Duplicates: Before importing any new skill, search existing suites for overlaps. Present candidates to the user to merge, upgrade, or deprecate redundant skills.
2. Skill Frontmatter Standard
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.
- 8d ago First seen · 45 lines · 731 tokens per session scan A a302d9ef73df
VibeCode-Protocol-Suite AGENTS.md is an instructions file published in the GitHub repository J-StaR-Films-Studios/VibeCode-Protocol-Suite (24 stars, last pushed 3d ago), licensed ISC. It adds 731 tokens to every session, about $0.0037 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
ai-agent-rules-generator ui-design.instructions.md
Glitch Payment Gateway admin UI design rules — mandatory element & component reference for WooCommerce settings.
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 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.
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 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).