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 skills add int2t05/engineering-skills --skill context-engineeringgit clone --depth 1 https://github.com/int2t05/engineering-skillsWrote 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/skills/int2t05/engineering-skills/context-engineering)<a href="https://agentmods.dev/skills/int2t05/engineering-skills/context-engineering"><img src="https://agentmods.dev/badge/skills/int2t05/engineering-skills/context-engineering/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/skills/int2t05/engineering-skills/context-engineering"><img src="https://agentmods.dev/badge/skills/int2t05/engineering-skills/context-engineering.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.00029 | $0.00265 |
| Opus 5.5 | $0.00012 | $0.00106 |
| Sonnet 5.5 | $0.00006 | $0.00053 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
context-engineering 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 10d 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.
What it actually says
Context Engineering
When to use
- Assemble relevant context or explain an existing code path.
Not for: handoff for transferring work; research for external investigation.
Steps
-
Choose explanation or execution-context mode and identify audience and exact question.
-
Trace actual definitions, callers, entry points and tests; distinguish instructions from external or quoted data.
-
Explain purpose, inputs, meaningful calls and outputs, or provide task goals, constraints, selected paths and verification commands.
-
Reconcile conflicts or ask about unresolved decisions; preserve confirmed context during compaction.
Verify
- Symbols and paths exist; the explanation follows actual calls and avoids irrelevant repository dumps.
References
- engineering-principles.md — shared decision boundaries, scope and verification.
- references/context-strategies.md — context packing strategies (brain dump, selective include, hierarchical summary), MCP integration table, anti-patterns.
- references/code-explanation.md — explaining existing code and giving codebase tours to a user
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago Changed · -61 lines · -38 tokens per session 1e1e6ae06c19
- 16d ago Changed · +1 lines 9e076c2abaee
- 1mo ago First seen · 93 lines · 67 tokens per session scan A 34176d6d1500
context-engineering is a skill published in the GitHub repository int2t05/engineering-skills (3 stars, last pushed 11d ago), licensed MIT. It adds 29 tokens to every session and 265 once invoked, about $0.0001 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-31.
Other skills, from other repositories
design-reviewer
Use after AC and before RED for any wave that ships UI. Performs component API audit against installed dist files, produces per-route mockup, defines visual ACs, flags design-system gaps. Output written to .wave/dr.md.
plan
Analyzes architecture, selects patterns, assesses testability, then decomposes work into ordered TDD tasks with exact verification commands and explicit acceptance mapping. Works from an approved spec (zuvo:brainstorm output) or directly from a user-provided description.
test-audit
Audit test suites for T1-T4 violations using AST analysis, mock detection, and multi-stage synthesis. Invoke when user asks to audit tests, check test quality, find mock violations, review test effectiveness, or inspect test suites for over-mocking. Triggers automatic rewrites when quality gates fail.
Eval-Driven Skill Design
A review guide for new coding-agent skills that checks whether each skill has both examples it should catch and examples it should ignore, plus evaluation setup.
pr-workflow
Crear pull requests completas con descripcion, labels y reviewers.
x-qdev
A compact development workflow for a small, clearly defined code change. It keeps the requirement, initially failing tests, implementation, and real verification results in one task document, following TDD, or test-driven development.