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/danielvm-git/bigpowersWrote 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/danielvm-git/bigpowers/survey-context)<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/survey-context"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/survey-context/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/danielvm-git/bigpowers/survey-context"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/survey-context.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.00063 | $0.01481 |
| Opus 5.5 | $0.00025 | $0.00592 |
| Sonnet 5.5 | $0.00013 | $0.00296 |
| Haiku 4.5 | $0.00006 | $0.00148 |
Grade A, and why
survey-context 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 1mo 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
story: e82s02
Survey Context
Read the project's current state and give a phase map + next-skill recommendation. This is the "where am I?" skill — run it at the start of every task.
Use this vs map-codebase:
survey-contextconsumes existing specs and docs (fast; does not re-derive).map-codebasebuilds the tech-stack doc from scratch by scanning the codebase. Runmap-codebasewhenspecs/tech-architecture/tech-stack.mddoesn't exist yet; runsurvey-contextwhen it does.
HARD GATE — Read specs/ files before suggesting next steps. If state.yaml is stale or contradicts the codebase, request clarification rather than assuming intent.
Orchestrate-project 6 phases: Phase 1 Discover - Phase 2 Elaborate - Phase 3 Plan - Phase 4 Build - Phase 5 Verify - Phase 6 Release
Process
Timing:
bash scripts/bp-timing.sh start survey-contextat invocation;bash scripts/bp-timing.sh end survey-contextbefore handoff.
1. Read CONVENTIONS.md
If CONVENTIONS.md exists at the project root, read it first. It contains the rules all agents must follow in this project.
2. Read specs/ (YAML-first)
Scan the specs/ directory if it exists:
specs/
├── state.yaml → session: active_flow, epic, git, handoff
├── release-plan.yaml → target version, WSJF epic index
├── execution-status.yaml → flat story/epic status
├── planning-status.yaml → discover-phase checklist (optional)
├── requirements/
│ ├── VISION_LATEST.yaml
│ ├── SCOPE_LATEST.yaml
│ └── GLOSSARY_LATEST.yaml
├── plans/ → TECH_STACK, TEST_PLAN, etc.
├── epics/ → eNN shards (flat yaml or eNN/stories/)
└── bugs/ → BUG-*.md + registry.yaml
For each YAML file found, note: exists? keys populated? handoff.next_skill?
Legacy markdown (specs/archive/STATE.md, RELEASE-PLAN.md) is not SoT if YAML exists.
→ verify: bash scripts/validate-specs-yaml.sh
3. Read CLAUDE.md
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.
- 1mo ago First seen · 140 lines · 63 tokens per session scan A 44471a346f32
survey-context is a cursor rule published in the GitHub repository danielvm-git/bigpowers (267 stars, last pushed 27d ago), licensed MIT. It adds 63 tokens to every session and 1,481 once invoked, about $0.0003 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-09-03.
Other cursor rules, from other repositories
payload-cms
Payload CMS: collections, fields, hooks, access control, admin UI.
monorepo
Monorepo: workspace references, shared packages, boundaries.
pnpm
PNPM: workspace monorepos, efficient package management.
ai-dev-os-ticket
Generates a ticket (local file or GitHub Issue) with implementation summary and checklist candidates derived from AI Dev OS guidelines. Used to create structured implementation tasks.
agent-workflow-orchestration
Mandatory PM-orchestrated subagent workflow — main agent is manager, no separate PM subagent.
12-new-project
Workflow for starting a new app from this template - rebranding, identity, cleanup and first feature.