Borrowing it
Nothing to install: this file belongs to serialx/vibecore. 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/serialx/vibecore/main/AGENTS.mdgit clone --depth 1 https://github.com/serialx/vibecoreWrote 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/serialx/vibecore/agents-md)<a href="https://agentmods.dev/instructions/serialx/vibecore/agents-md"><img src="https://agentmods.dev/badge/instructions/serialx/vibecore/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/serialx/vibecore/agents-md"><img src="https://agentmods.dev/badge/instructions/serialx/vibecore/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.00662 | $0.00662 |
| Opus 5.5 | $0.00265 | $0.00265 |
| Sonnet 5.5 | $0.00132 | $0.00132 |
| Haiku 4.5 | $0.00066 | $0.00066 |
Grade A, and why
vibecore 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 2mo 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
src/vibecoreholds the app (main.py), Flow Mode orchestration (flow.py), and subpackages for agents, tools, widgets, session, models, and mcp.- Entry points are
cli.pyandmain.py; defaults and prompts live insettings.pyandprompts/. - Flow and multi-agent samples are under
examples/; reference docs stay indocs/. - Tests mirror runtime modules in
tests/, with fixtures intests/fixturesand harness helpers intests/_harness.
Build, Test, and Development Commands
uv sync— provision the dev environment againstuv.lock.uv run vibecore— launch the TUI locally; (NEVER RUN THIS)uv run vibecore --print -p 'prompt'— launch vibecore in pipe mode. non-TUI. (USE THIS INSTEAD OF TUI)uv run pytest …— run the suite or scoped folders liketests/ui.uv run ruff check ./uv run ruff format .— lint and auto-format.uv run pyright— type-check before requesting review.
Coding Style & Naming Conventions
- Python 3.11, 4-space indentation, 120-character lines, double quotes via Ruff.
- Use snake_case for modules, functions, variables; PascalCase for classes and TypedDicts.
- Keep public APIs typed—
py.typedmeans downstream users rely on annotations. - Place new tools, widgets, or agents beside existing peers to keep modules focused.
Testing Guidelines
- pytest runs in strict asyncio mode; decorate async tests with
pytest.mark.asyncio. - Name files
test_*.py, reuse fixtures, and mirror new runtime code with matching tests. - UI changes touching message widgets must refresh
tests/ui/test_message_snapshots.py. - Run full
uv run pytestplus targeted suites before opening a PR.
Textual & UI Development Tips
- Consult Textual source in
.venv/lib/python3.11/site-packages/textual/when extending widgets—docs lag the implementation. - Textual ignores CSS
@keyframes; use widgetanimate()helpers for motion. - Streaming handlers in
handlers/expect incremental updates—ensure new widgets cooperate with that flow.
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.
- 2mo ago First seen · 43 lines · 662 tokens per session scan A 518ebd6568e4
vibecore AGENTS.md is an instructions file published in the GitHub repository serialx/vibecore (23 stars, last pushed 9mo ago), licensed MIT. It adds 662 tokens to every session, about $0.0026 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-30.
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.