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 mdsakalu/agent-plugins --skill reflecting-on-skillsgit clone --depth 1 https://github.com/mdsakalu/agent-pluginsWrote 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/mdsakalu/agent-plugins/reflecting-on-skills)<a href="https://agentmods.dev/skills/mdsakalu/agent-plugins/reflecting-on-skills"><img src="https://agentmods.dev/badge/skills/mdsakalu/agent-plugins/reflecting-on-skills/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/mdsakalu/agent-plugins/reflecting-on-skills"><img src="https://agentmods.dev/badge/skills/mdsakalu/agent-plugins/reflecting-on-skills.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.00041 | $0.01235 |
| Opus 5 | $0.00020 | $0.00617 |
| Sonnet 5 | $0.00008 | $0.00247 |
| Haiku 4.5 | $0.00004 | $0.00123 |
Grade B, and why
reflecting-on-skills 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 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
This skill is triggered by a PostToolUse hook in `~/.claude/settings.json`: How it starts
The opening of the file, as written. The whole thing — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reflecting on Skills
This skill is automatically triggered after any other skill completes (via a PostToolUse hook).
Platform Compatibility
Claude Code Only: This skill uses PostToolUse hooks and the Task tool for background subagent execution. These features are specific to Claude Code and not available in Claude apps or via the API.
For the cross-platform Agent Skills specification, see agentskills.io.
Instructions
When invoked after another skill completes:
-
Identify the skill - Determine which skill was just used from conversation context
-
Launch background analysis - Use the Task tool:
Task tool with: subagent_type: "general-purpose" run_in_background: true prompt: [see below] -
Subagent prompt template:
Analyze the skill that was just used in this conversation. 1. Read the skill's SKILL.md file at: ~/.claude/skills/[skill-name]/SKILL.md 2. Review the conversation to identify: - Errors or exceptions encountered - Unclear or missing instructions that caused confusion - Edge cases the skill didn't handle - Inefficiencies or unnecessary steps - Deviations from the skill's guidance (may indicate gaps) 3. If issues found, draft SPECIFIC improvements: - Exact text to add/change in SKILL.md - Keep changes minimal and focused - Only address observed issues, not hypotheticals 4. If improvements warranted, use AskUserQuestion: - Present the issue observed - Show the proposed change - Ask: "Apply this improvement to [skill-name]?" 5. If approved, use Edit tool to update the skill's SKILL.md If no issues observed, complete silently without prompting. -
Continue conversation - Don't wait for reflection to complete
Hook Configuration
This skill is triggered by a PostToolUse hook in ~/.claude/settings.json:
{
"hooks": {
"PostToolUse": [
{
"matcher": "Skill",
"hooks": [
{
"type": "command",
"command": "python3 ~/.claude/hooks/post-skill-reflect.py"
}
]
}
]
}
}
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 First seen · 153 lines · 41 tokens per session scan B d0f8eb650e62
reflecting-on-skills is a skill published in the GitHub repository mdsakalu/agent-plugins (4 stars, last pushed 3mo ago), licensed MIT. It adds 41 tokens to every session and 1,235 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…
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…