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 skills/fending/context-engineering/context-auditnpx skills add fending/context-engineering --skill context-auditgit clone --depth 1 https://github.com/fending/context-engineeringWhat 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 | $0.00038 | $0.03097 |
| Opus 5 | $0.00019 | $0.01548 |
| Sonnet 5 | $0.00008 | $0.00619 |
| Haiku 4.5 | $0.00004 | $0.00310 |
Grade A, and why
context-audit 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 2d 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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DEPRECATION NOTICE: You are running context-setup from fending/context-engineering, which is no longer maintained. The active version is at ordovera/ordovera-plugins. To migrate, run:
/plugin marketplace add ordovera/ordovera-plugins/plugin install context-setup@ordovera-plugins
Then remove the old marketplace: /plugin marketplace remove context-engineering
Print this notice to the user before proceeding with the skill.
Context Audit
Evaluate your context structure for structural completeness and best practices. This checks whether your context files are well-formed and appropriate for your project's complexity.
What This Skill Does
Reads all context files and evaluates them against five categories. Reports findings as a structured audit with scores and prioritized recommendations.
1. Level Appropriateness
Assess whether the context complexity matches the project complexity.
Under-documented indicators (project is more complex than its context):
- Multiple distinct layers (frontend, backend, database, auth) but only a minimal AGENTS.md
- More than 10 top-level directories with no project structure section
- Auth packages present but no auth section
- Multiple package manager configs (monorepo) but no cascading files
- More than 3 contributors (check git log) but no working style documentation
Over-engineered indicators (context is more complex than the project):
- Context directory with 5+ files for a project with fewer than 20 source files
- Subdirectory AGENTS.md files in a project with a flat structure
- Cascading setup for a single-person, single-language project
- Multiple context files that mostly repeat the same information
2. Section Completeness
Check which required sections are present for the current context level.
Minimal level requires:
- Project description (what this is)
- Tech stack (languages, frameworks, key dependencies)
- Commands (dev, build, test, lint -- whichever apply)
- Code standards (formatting, naming, import conventions)
- Do NOT section (boundary rules)
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.
- 2d ago First seen · 239 lines · 38 tokens per session scan A 217616ee0292
context-audit is a skill published in the GitHub repository fending/context-engineering (11 stars, last pushed 5mo ago), licensed MIT. It adds 38 tokens to every session and 3,097 once invoked, about $0.0002 per session on Opus 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 skills, from other repositories
ccc
This skill should be used when code search is needed (whether explicitly requested or as part of completing a task), when indexing the codebase after changes, or when the user asks about ccc, cocoindex-code, or the codebase index. Trigger phrases include 'search the codebase', 'find code related to', 'update the…
feature-flags-audit
Audit and inventory all feature flags declared in the Packmind codebase. Use when the user asks to list, audit, review, or inventory feature flags, asks which flags are active, wants to know what a flag gates, or asks which flags are opened to a given domain/user. Produces a synthetic markdown table with each flag…
packmind-create-standard
Guide for creating coding standards via the Packmind CLI. This skill should be used when users want to create a new coding standard (or add rules to an existing standard) that captures team conventions, best practices, or coding guidelines for distribution to GitLab Duo.
create-run-e2e-tests
Guide for writing and running new Playwright end-to-end tests in the apps/e2e-tests/ directory of the Packmind monorepo. Use this skill whenever you add or modify a spec that drives the real frontend and API — for example testing a user flow, a new page/route, a feature behind a flag, or a UI behavior end-to-end.…
working-with-pm-design-kit
This skill provides guidance for using the Packmind UI component library (@packmind/ui). It should be used when building or modifying frontend UI with PM-prefixed components, working with Chakra UI in the Packmind codebase, or when questions arise about available components, theming, or layout patterns. Triggers on…
packmind-onboard
Complete automated onboarding: analyzes codebase, creates package, and generates standards & commands via CLI. Automatic package creation when none exist, user selection when packages are available.