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/kesteva/cyboflow/agents-mdgit clone --depth 1 https://github.com/kesteva/cyboflowWrote 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/kesteva/cyboflow/agents-md)<a href="https://agentmods.dev/instructions/kesteva/cyboflow/agents-md"><img src="https://agentmods.dev/badge/instructions/kesteva/cyboflow/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 | $0.01439 | $0.01439 |
| Opus 5 | $0.00720 | $0.00720 |
| Sonnet 5 | $0.00288 | $0.00288 |
| Haiku 4.5 | $0.00144 | $0.00144 |
Grade A, and why
cyboflow 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 4d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
- Root
pnpmworkspace with packages:main/(Electron main process, TypeScript),frontend/(React + Vite),shared/(shared types), andtests/(Playwright E2E). - Key paths:
main/src/{services,ipc,utils}/,frontend/src/{components,hooks,stores,utils}/,main/assets/,scripts/. - Build artifacts:
frontend/dist/,main/dist/, packaged outputdist-electron/.
Build, Test, and Development Commands
- Dev app:
pnpm dev(spawns frontend + Electron). - Build all:
pnpm build(frontend, main, then electron package). - Package (examples):
pnpm build:mac:arm64,pnpm build:mac:x64(macOS-only; per-arch — the universalbuild:maccurrently fails on the bundled agent binaries, seedocs/RELEASE-RUNBOOK.md). - Lint:
pnpm lint; Type-check:pnpm typecheck(runs per package). - Final code-change gate:
pnpm test:unit(main + frontend vitest + schema parity + build scripts) — for a settled tree. While work is in progress, and always inside a sprint lane, run scoped tests instead:cd main && npx vitest run <paths>. See "Testing Guidelines". - E2E (
pnpm test:e2e,pnpm test:ui): drives the built Electron bundle via Playwright_electron.launch(); needs a real display, so it is NOT the headless gate. Seedocs/ARCHITECTURE.md"Build & Run". - Main unit tests (if added):
pnpm --filter main test, coverage:pnpm --filter main run test:coverage.
Coding Style & Naming Conventions
- Use TypeScript throughout; follow ESLint configs in
frontend/eslint.config.jsandmain/eslint.config.js. - Indentation 2 spaces; prefer explicit types at module boundaries.
- Naming:
camelCasefor variables/functions,PascalCasefor React components/types,kebab-casefor filenames (React files may match component name). - Run
pnpm lint && pnpm typecheckbefore sending PRs.
Testing Guidelines
- Which tests to run when.
pnpm test:unitis the final gate, not the per-change gate — it runs two full vitest suites, so several agents running it at once pin every core.- Inside a sprint/ship lane (you are an implement / write-tests / task-verify subagent): run ONLY the tests covering your files —
cd main && npx vitest run <paths>. Do not runpnpm test:unit. Lanes fan out into ONE shared worktree, so a full-suite run there also executes your siblings' half-finished uncommitted edits: unrelated failures are noise and a green result proves nothing about your task. The full suite issprint-verify's job, once, over the combined state. - Final verification (
sprint-verify, or an interactive session finishing a change):pnpm test:unitonce, over the settled tree. SeeCLAUDE.mdfor why E2E is not the gate. - Prefer
npx vitest runper workspace overpnpm --filter— filter recursion has broken bin PATH resolution in this repo.
- Inside a sprint/ship lane (you are an implement / write-tests / task-verify subagent): run ONLY the tests covering your files —
- For backend logic in
main/, use Vitest colocated undermain/src/**/__tests__or*.spec.ts; frontend likewise. - E2E tests live in
tests/*.spec.ts(Playwright); they drive the built Electron bundle via_electron.launch()and need a real display (the host-Node ABI is restored automatically by the nextpnpm test:unit; for a directnpx vitest run, usenode scripts/ensure-sqlite-abi.mjs host).
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.
- 4d ago First seen · 54 lines · 1,439 tokens per session scan A f21a3f95f6f4
cyboflow AGENTS.md is an instructions file published in the GitHub repository kesteva/cyboflow (55 stars, last pushed 5d ago), licensed MIT. It adds 1,439 tokens to every session, about $0.0072 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
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.