Skip to main content

What is a context?

A context is a security knowledge bundle the agent loads before starting an engagement. It gives the agent domain expertise: methodology, techniques, tools, and reporting guidance for a specific type of security work. Contexts are served via the rifteo-context-mcp MCP server and retrieved on demand through natural language. Unlike skills (which define a specific technique), contexts define the full engagement methodology: the phases to follow, what to test, how to validate findings, and how to report.

Install the MCP server

Register with all detected agents at once:
Or register with a specific agent:
Supports 15 agents: Claude Code, Cursor, Windsurf, Gemini CLI, Cline, Kiro, Codex, OpenCode, Amp, Continue, GitHub Copilot, Aider Desk, Roo Code, OpenHands, Goose.

Using a context

Once the MCP server is registered, ask your agent in plain language:
The agent automatically loads the right level (L1 for an overview, L2 when it needs deep methodology detail).

Available contexts

Context anatomy

Every context lives in its own directory with a single required file:

CONTEXT.md

The core of every context. It has a frontmatter block and a body structured in three levels:
See CONTEXT_GUIDE.md for the full format reference including optional fields.

The 3-tier loading system

Each context has three levels of detail. The MCP server loads the right level based on what the agent needs, keeping token usage low.

Context vs skill

Contexts and skills work together: a context defines the engagement methodology and references relevant skills at each phase.

Naming conventions

Next step

Ready to write a context? Follow the CONTEXT_GUIDE.md in the community repo.