context-report

context-report is a skill for Claude Code, Codex from moberghr/mtk-agent-toolkit. It costs 32 tokens per session (2,311 once invoked), scanned B, original, MIT.

A diagnostic report of the MTK configuration currently active in a repository, including its technology stack, rules, references, domains, linters, and hooks.

In plain words
What is it for?
Use it after setup, while onboarding to a repository, or when debugging review behavior and configuration.
Why use it?
It explains what guidance is loaded and helps investigate missing checks or unexpected review results.

Skill for Claude CodeCodex

Part of the mtk plugin — 45 skills, 6 agents, 7 hooks, 1 MCP server shipped together

Install

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.

agentmods
npx agentmods add skills/moberghr/mtk-agent-toolkit/context-report
Any agent
npx skills add moberghr/mtk-agent-toolkit --skill context-report
Clone the repo
git clone --depth 1 https://github.com/moberghr/mtk-agent-toolkit

Made for: Claude Code, Codex.

Or install mtk, the plugin that ships this one along with the rest of its 45 skills, 6 agents, 7 hooks, 1 MCP server.

Wrote 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.

agentmods badge for context-report

README.md
[![agentmods](https://agentmods.dev/badge/skills/moberghr/mtk-agent-toolkit/context-report.svg)](https://agentmods.dev/skills/moberghr/mtk-agent-toolkit/context-report)
Your own site
<a href="https://agentmods.dev/skills/moberghr/mtk-agent-toolkit/context-report"><img src="https://agentmods.dev/badge/skills/moberghr/mtk-agent-toolkit/context-report.svg" alt="Measured on agentmods" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,311 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00032 $0.02311
Opus 5 $0.00016 $0.01156
Sonnet 5 $0.00006 $0.00462
Haiku 4.5 $0.00003 $0.00231

Measured 5d ago against content hash fe40c1a232ea, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade B, and why

context-report scanned grade B with 1 finding 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 5d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

cat .claude/tech-stack 2>/dev/null || echo "(not set)"
.claude/skills/context-report/SKILL.md · 253 lines

How it starts

The opening of the file, as written. The whole thing — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Context Report

Overview

Diagnostic snapshot of the MTK toolkit's active configuration. Shows what's loaded, what's not, and why. Use this when debugging review behavior, understanding why a linter pattern fired, or verifying that a domain pack is active.

When To Use

  • After running /mtk-setup to verify configuration
  • When a review misses something and you want to see what references loaded
  • When onboarding to a new repo to understand the MTK setup
  • When debugging linter false positives or false negatives

When NOT To Use

  • As part of normal implementation flow (context-engineering handles loading)

Workflow

STEP 1 — Gather state

Collect the following diagnostic data and present it in a single structured report.

1a. Tech Stack
echo "--- Tech Stack ---"
cat .claude/tech-stack 2>/dev/null || echo "(not set)"
if [ -f .claude/tech-stack-pm ]; then echo "Package Manager: $(cat .claude/tech-stack-pm)"; fi
1b. Active Domains
echo "--- Domains ---"
if [ -f .claude/domains ]; then
  cat .claude/domains
else
  echo "(none — create .claude/domains with one domain per line to activate domain packs)"
fi
1c. Linter Packs
echo "--- Linter Packs ---"
PATTERNS_DIR="hooks/linter-patterns"

echo "Core:"
if [ -d "$PATTERNS_DIR/core" ]; then
  for f in "$PATTERNS_DIR"/core/*.txt; do
    [ -f "$f" ] && echo "  $(basename "$f") ($(grep -c '^[^#]' "$f" 2>/dev/null || echo 0) rules)"
  done
else
  echo "  (flat-file layout — pre-6.2)"
fi

STACK="$(cat .claude/tech-stack 2>/dev/null | tr -d '[:space:]')"
if [ -n "$STACK" ]; then
  echo "Stack ($STACK):"
  if [ -d "$PATTERNS_DIR/stack-$STACK" ]; then
    for f in "$PATTERNS_DIR"/stack-"$STACK"/*.txt; do
      [ -f "$f" ] && echo "  $(basename "$f") ($(grep -c '^[^#]' "$f" 2>/dev/null || echo 0) rules)"
    done
  else
    echo "  (not found)"
  fi
fi

echo "Domain:"
if [ -f .claude/domains ]; then
  while IFS= read -r domain; do
    domain="$(echo "$domain" | tr -d '[:space:]')"
    [ -z "$domain" ] && continue
    [[ "$domain" == \#* ]] && continue
    if [ -d "$PATTERNS_DIR/domain-$domain" ]; then
      for f in "$PATTERNS_DIR"/domain-"$domain"/*.txt; do
        [ -f "$f" ] && echo "  $domain/$(basename "$f") ($(grep -c '^[^#]' "$f" 2>/dev/null || echo 0) rules)"
      done
    else
      echo "  $domain: (pack not found at $PATTERNS_DIR/domain-$domain/)"
    fi
  done < .claude/domains
else
  echo "  (no .claude/domains file)"
fi

echo "Project-local:"
project_count=0
if [ -d "$PATTERNS_DIR/project" ]; then
  for f in "$PATTERNS_DIR"/project/*.txt; do
    [ -f "$f" ] && echo "  $(basename "$f") ($(grep -c '^[^#]' "$f" 2>/dev/null || echo 0) rules)" && project_count=$((project_count+1))
  done
fi
[ "$project_count" -eq 0 ] && echo "  (none — add .txt files to hooks/linter-patterns/project/)"

Read the full file on GitHub · 253 lines

Changes

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.

  1. 5d ago First seen · 253 lines · 32 tokens per session scan B fe40c1a232ea

Subscribe to this mod's changes

context-report is a skill published in the GitHub repository moberghr/mtk-agent-toolkit (7 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 2,311 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens