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 escoffier-labs/skillet --skill stocktakegit clone --depth 1 https://github.com/escoffier-labs/skilletWrote 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/escoffier-labs/skillet/stocktake)<a href="https://agentmods.dev/skills/escoffier-labs/skillet/stocktake"><img src="https://agentmods.dev/badge/skills/escoffier-labs/skillet/stocktake/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/escoffier-labs/skillet/stocktake"><img src="https://agentmods.dev/badge/skills/escoffier-labs/skillet/stocktake.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.00050 | $0.01192 |
| Opus 5 | $0.00025 | $0.00596 |
| Sonnet 5 | $0.00010 | $0.00238 |
| Haiku 4.5 | $0.00005 | $0.00119 |
Grade A, and why
stocktake 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 11d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
stocktake
A stocktake records what the project actually uses before changing what it orders. Dependency work starts from manifests, resolved versions, runtime pins, generated clients, and CI configuration. The requested version is only one line in that inventory.
Modes
- AUDIT reports outdated, unsupported, vulnerable, duplicated, or unused dependencies without changing the repository.
- UPDATE applies a requested version change or an accepted audit finding.
- MIGRATE handles a major version, runtime, package manager, or toolchain boundary with required source and configuration changes.
If the user asks only for an audit, stop after the backlog. Do not turn discovery into a lockfile rewrite.
1. Define the boundary
Pin the scope before running an updater:
- named package, runtime, toolchain, or manifest
- requested target version or allowed version range
- applications and libraries affected
- compatibility floors that must remain supported
- whether security remediation changes the priority
Split unrelated major upgrades. A runtime migration, framework major, and package-manager change are separate compatibility boundaries even when one command can update all three.
2. Inventory resolved state
Read every source that can select or constrain a version:
- package manifests and workspace roots
- lockfiles, checksums, and vendored dependency records
- runtime and toolchain pins
- CI actions, build images, containers, and deployment configuration
- generated clients, code generators, plugins, and peer dependencies
- repository instructions that prescribe supported versions
Record direct and transitive versions using the ecosystem's supported inspection command. Do not infer the resolved graph from a manifest range.
3. Establish the baseline
Run the project's documented checks before editing. Capture:
- install or dependency-resolution result
- focused tests for the affected subsystem
- full test or build result when practical
- relevant warnings and deprecation messages
What ships with it
2 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.
- 11d ago First seen · 144 lines · 50 tokens per session scan A ab503345eb37
stocktake is a skill published in the GitHub repository escoffier-labs/skillet (4 stars, last pushed 10d ago), licensed MIT. It adds 50 tokens to every session and 1,192 once invoked, about $0.0003 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-31.
Other skills, from other repositories
assess-interview-candidate
A structured hiring-assessment workflow that turns a candidate's résumé and a job description into reviewable evidence, interview questions, and an offline HTML report for interviewers.
task-clarifier
Deep need-clarification skill. Use only when the user explicitly invokes $task-clarifier. Once activated, keep asking until all three goals are met: the user fully understands their own needs, the AI fully understands the user's needs, and the user confirms the AI's understanding is correct. Do not intervene in task…
user-profile-keeper
Local user-profile maintenance skill for Codex, Claude Code, OpenClaw, OpenCode, and other agent harnesses. Use only when the user explicitly invokes $user-profile-keeper to create, initialize, update, query, correct, delete, export, or audit a local persistent user profile. It can extract durable collaboration…
run-history-skill-builder
Turn a completed task, browser flow, artifact pipeline, failure-recovery trace, or repeatedly refined workflow into a new reusable skill package or a reviewed skill-design plan. Use when the user asks to make a new skill from real run history, extract a reusable workflow from conversation/logs/files, summarize lessons…
run-history-skill-upgrader
Use real run evidence, validation failures, source drift, platform drift, and user feedback to plan and, only after explicit approval, apply structural upgrades to an existing skill. Use when the user asks to improve an existing skill from recent runs, recurring failures, outdated sources, excessive bloat, changed…
session-handoff-prompt
Create a concise continuation prompt that a fresh agent session can paste in to resume a long or degraded session. Use when the user asks for a handoff prompt, restart prompt, continuation prompt, context transfer, fresh-session resume, or a compact summary for opening a new session. Do not use for ordinary summaries…