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.
git clone --depth 1 https://github.com/varutasu/agent-pipelineWrote 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/rules/varutasu/agent-pipeline/agent-context-bootstrap)<a href="https://agentmods.dev/rules/varutasu/agent-pipeline/agent-context-bootstrap"><img src="https://agentmods.dev/badge/rules/varutasu/agent-pipeline/agent-context-bootstrap/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/rules/varutasu/agent-pipeline/agent-context-bootstrap"><img src="https://agentmods.dev/badge/rules/varutasu/agent-pipeline/agent-context-bootstrap.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.00410 | $0.00410 |
| Opus 5.5 | $0.00164 | $0.00164 |
| Sonnet 5.5 | $0.00082 | $0.00082 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
agent-context-bootstrap 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.
What it actually says
Agent context bootstrap
If the current workspace has no AGENTS.md at the repo root and no .cursor/rules/ directory, and the user is asking how to orient themselves in this codebase, set up AI guidance, reduce token use, deploy agent context, or scaffold rules and skills, suggest the bootstrap-agent-context skill before answering at length.
Phrase it as a one-line offer:
"This repo doesn't have an
AGENTS.mdor.cursor/rules/yet. I can run thebootstrap-agent-contextskill to draft them — it detects the stack and stops before committing for your review. Want me to start?"
Then wait for confirmation before reading the skill.
When NOT to suggest
- The repo already has
AGENTS.mdor.cursor/rules/*.mdc. (The skill is for first-time setup.) - The user is asking a narrow code question that doesn't depend on broad orientation.
- The user has explicitly declined the bootstrap in this conversation.
- The repo is clearly read-only or not the user's (vendored, cloned for reference, third-party).
This is a soft nudge, not a hard requirement. If grep + read solves the user's question in one or two calls, do that instead.
If the repo IS already bootstrapped
If the workspace has .agent-context-manifest.yml at the root and the user asks about updates, pipeline version, drift, or out-of-date rules/skills/agents, suggest the sync-agent-context skill instead:
"This repo has an agent-pipeline manifest at version X. I can run the
sync-agent-contextskill to compare each installed artifact against the latest pipeline source and propose updates per file. Want me to start?"
Same soft-nudge etiquette — skip if the question doesn't depend on freshness.
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 · 32 lines · 410 tokens per session scan A deb3df52cdd7
agent-context-bootstrap is a cursor rule published in the GitHub repository varutasu/agent-pipeline (2 stars, last pushed 2mo ago), licensed MIT. It adds 410 tokens to every session, about $0.0016 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.