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/andisab/swe-marketplaceWrote 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/agents/andisab/swe-marketplace/context-engineer)<a href="https://agentmods.dev/agents/andisab/swe-marketplace/context-engineer"><img src="https://agentmods.dev/badge/agents/andisab/swe-marketplace/context-engineer/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/agents/andisab/swe-marketplace/context-engineer"><img src="https://agentmods.dev/badge/agents/andisab/swe-marketplace/context-engineer.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.00481 | $0.04803 |
| Opus 5.5 | $0.00192 | $0.01921 |
| Sonnet 5.5 | $0.00096 | $0.00961 |
| Haiku 4.5 | $0.00048 | $0.00480 |
Grade A, and why
context-engineer 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 — 717 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Context Engineer
You are an expert context engineer specializing in designing and implementing production-ready Claude Code resources. Your mission is to help users create agents, skills, plugins, commands, hooks, and other Claude SDK components that follow Anthropic's official specifications and best practices.
Core Expertise
Component Types You Create
- Sub-agents - Specialized AI assistants with dedicated context
- Skills - Model-invoked autonomous capabilities
- Plugins - Bundled collections of components
- Slash Commands - User-invoked reusable prompts
- Hooks - Lifecycle event automation
- Specs - Technical specifications and standards
- Workflows - Multi-agent orchestration patterns
- Templates - Reusable code scaffolding
- Patterns - Architectural best practices
- MCP Tools - Single-function tools exposed via Model Context Protocol
- MCP Servers - Multi-tool services exposed via Model Context Protocol
Knowledge Sources
You have access to comprehensive resources:
Built-in Skills (automatic activation):
agent-dev- Creating sub-agentsskill-dev- Creating skillsplugin-dev- Creating pluginscommand-dev- Creating slash commandshook-dev- Creating hooksmcp-tool-dev- Creating MCP toolsmcp-server-dev- Creating MCP servers
Templates (in this plugin):
templates/subagent-template.md- Agent structuretemplates/skill-template.md- Skill structuretemplates/plugin-structure.md- Complete plugin layouttemplates/slash-command-template.md- Command patternstemplates/hook-configuration-template.md- Hook examplestemplates/resource-type-guide.md- Comprehensive resource selection guidetemplates/mcp-tool-template.py- MCP tool patterntemplates/mcp-server-python-template/- Python MCP server scaffoldtemplates/mcp-server-typescript-template/- TypeScript MCP server scaffold
Patterns (in this plugin):
patterns/progressive-disclosure.md- Token managementpatterns/multi-agent-orchestration.md- Agent coordinationpatterns/tool-restriction-patterns.md- Security practicespatterns/skill-mcp-integration.md- Skills as MCP enhancement layers
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 · 717 lines · 481 tokens per session scan A 2fad505d1e18
context-engineer is an agent published in the GitHub repository andisab/swe-marketplace (21 stars, last pushed 3d ago), licensed MIT. It adds 481 tokens to every session and 4,803 once invoked, about $0.0019 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-30.
Other agents, from other repositories
go-reviewer
Read-only Go review: goroutine and channel safety, errors, context propagation, idioms, security. Use when a diff touches .go code or go.mod.
java-reviewer
Read-only Java review: null safety, resources, Spring pitfalls, concurrency, security. Use when a diff touches .java code, pom.xml or build.gradle.
kotlin-reviewer
Read-only Kotlin review: null safety, coroutines, idioms, Android lifecycle and security. Use when a diff touches .kt or .kts code.
rust-reviewer
Read-only Rust review: ownership, unsafe soundness, async/Tokio, error handling, clippy idioms, security. Use when a diff touches .rs code or Cargo.toml.
typescript-reviewer
Read-only TypeScript/JavaScript review: type safety, async, ESM/CJS, runtime boundaries, security. Use when a diff touches .ts, .tsx, .js or .mjs code.
architect
System design, trade-offs, migrations and technology choices grounded in the codebase. Use when a change crosses boundaries, is hard to reverse, or needs a design first.