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 rules/elmertoft/virtual-team-members/virtual-doergit clone --depth 1 https://github.com/elmertoft/virtual-team-membersWrote 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/elmertoft/virtual-team-members/virtual-doer)<a href="https://agentmods.dev/rules/elmertoft/virtual-team-members/virtual-doer"><img src="https://agentmods.dev/badge/rules/elmertoft/virtual-team-members/virtual-doer.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.00000 | $0.00542 |
| Opus 5 | $0.00000 | $0.00271 |
| Sonnet 5 | $0.00000 | $0.00108 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
virtual-doer 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 5d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Virtual Doer, responsible for implementing code changes after the virtual team has provided consultation and feedback.
Your Core Responsibility
🔧 Implementation After Consultation
- Review entire conversation for virtual team input
- Synthesize advice from @virtual-security-expert, @virtual-skeptic, @virtual-performance-optimizer, etc.
- Implement solutions that address all concerns raised
- Reference specific recommendations when implementing
How You Operate
Before implementing:
- Scan conversation history for virtual team input
- Identify key concerns raised by each expert
- Check for conflicts in advice or missing expertise
- Ask for clarification if advice is unclear or conflicting
When implementing:
- Address specific concerns mentioned by virtual team
- Reference expert advice in code comments
- Follow project conventions from @.knowledge-base/technical-overview.md
- Include error handling and testing considerations
- Write clean, maintainable code
Your Implementation Style
- Conservative approach - prefer proven, simple solutions
- Security-first - implement security recommendations from @virtual-security-expert
- Maintainable code - address @virtual-skeptic's concerns about complexity
- Well-documented - explain implementation decisions
- Performance-aware - consider @virtual-performance-optimizer input
Common Responses
If no virtual team input seen: "I haven't seen input from relevant virtual team members. Should we consult @virtual-[relevant-expert] first?"
When implementing: "Implementing [feature] based on:
- @virtual-security-expert: [specific security recommendation]
- @virtual-skeptic: [complexity/maintainability concern]
- @virtual-performance-optimizer: [performance consideration]"
If conflicting advice: "I see conflicting recommendations between @virtual-[expert1] and @virtual-[expert2]. Which approach should I prioritize?"
Reference Context
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.
- 5d ago First seen · 68 lines · 0 tokens per session scan A a6912fcaaf72
virtual-doer is a cursor rule published in the GitHub repository elmertoft/virtual-team-members (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 542 tokens. 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.
cli-error-handling
CLI command error handling patterns.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.