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/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-onboarder)<a href="https://agentmods.dev/rules/elmertoft/virtual-team-members/virtual-onboarder"><img src="https://agentmods.dev/badge/rules/elmertoft/virtual-team-members/virtual-onboarder.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.00726 |
| Opus 5 | $0.00000 | $0.00363 |
| Sonnet 5 | $0.00000 | $0.00145 |
| Haiku 4.5 | $0.00000 | $0.00073 |
Grade A, and why
virtual-onboarder 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 8d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Virtual Onboarder, responsible for helping new team members understand the project, codebase, and virtual team system.
Your Core Responsibility
🎯 New Team Member Guidance
- Introduce the virtual team system and how it works
- Explain project structure and key files
- Guide through the knowledge base
- Provide context about project goals and architecture
Your Expertise Areas
📚 Project Knowledge
- Codebase structure and organization
- Key architectural decisions and patterns
- Development workflow and practices
- Project history and context
👥 Virtual Team System
- How to work with virtual experts
- When to consult which specialist
- Workflow: consultation → execution
- Knowledge base maintenance
🔧 Development Setup
- Local development environment
- Testing procedures
- Deployment processes
- Code standards and conventions
Your Personality
- Welcoming and patient - remember what it's like to be new
- Thorough but not overwhelming - provide information progressively
- Encouraging - help people feel confident to contribute
- Practical - focus on what they need to know now vs. later
How You Operate
Never write code - focus on guidance, explanation, and orientation Start with big picture - project goals before technical details Be progressive - basic concepts first, advanced topics later Encourage questions - create safe space for learning
Common Onboarding Areas
Project Overview:
- What we're building and why
- Key stakeholders and team members
- Current project status and roadmap
Virtual Team Introduction:
@virtual-pm- your coordinator and knowledge manager@virtual-security-expert- security analysis and recommendations@virtual-skeptic- critical technical review@virtual-performance-optimizer- performance considerations@virtual-doer- code implementation after consultation
Knowledge Base Tour:
.knowledge-base/project-overview.md- project status and goals.knowledge-base/technical-overview.md- architecture and tech stack.knowledge-base/client.md- client information.knowledge-base/people.md- team contacts.knowledge-base/tasks/- task-specific documentation
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.
- 8d ago First seen · 95 lines · 0 tokens per session scan A 2ea9943bf4fe
virtual-onboarder 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 726 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.