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 KimYx0207/Meta_Kim --skill same-set-reusable-flow-for-project-file-inventorgit clone --depth 1 https://github.com/KimYx0207/Meta_KimWrote 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/kimyx0207/meta_kim/same-set-reusable-flow-for-project-file-inventor)<a href="https://agentmods.dev/skills/kimyx0207/meta_kim/same-set-reusable-flow-for-project-file-inventor"><img src="https://agentmods.dev/badge/skills/kimyx0207/meta_kim/same-set-reusable-flow-for-project-file-inventor/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/kimyx0207/meta_kim/same-set-reusable-flow-for-project-file-inventor"><img src="https://agentmods.dev/badge/skills/kimyx0207/meta_kim/same-set-reusable-flow-for-project-file-inventor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 80 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00045 | $0.01143 |
| Opus 5 | $0.00023 | $0.00571 |
| Sonnet 5 | $0.00009 | $0.00229 |
| Haiku 4.5 | $0.00005 | $0.00114 |
Grade A, and why
same-set-reusable-flow-for-project-file-inventor 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 13d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project File Inventory Classification
Use this skill when a Meta_Kim workspace has too many files and the user needs to know which are useful, generated, risky, or safe to ignore.
Goal
Produce a source-backed inventory, not a cleanup guess. The output should help the user decide what to keep, commit, ignore, or inspect again.
Required Evidence
Start with read-only evidence:
git status --short --branchgit ls-filesgit ls-files --others --exclude-standardgit check-ignore -v <path>for suspicious ignored pathsrg -n "<filename-or-command>" package.json docs scripts tests canonical configfor tracked candidatesnpm runscript inventory frompackage.json
Do not classify a tracked file as removable only because it has few references. Check package scripts, tests, docs, sync scripts, setup scripts, and contracts first.
Classification Buckets
- Core source:
canonical/,config/contracts/,config/capability-index/, durable scripts, package scripts, and tests that define behavior. - Runtime projection:
.claude/,.agents/,.cursor/,openclaw/,.codex/mirrors generated from canonical sources or sync scripts. - Generated evidence:
.meta-kim/state/default/, graph outputs, reports, SQLite run state, smoke artifacts, and temporary proof files. - Planning continuity:
task_plan.md,findings.md,progress.md; keep during active work even if ignored. - Reference docs: tracked docs and plans that explain product, architecture, contracts, or release decisions.
- Suspicious or cleanup candidate: files with no package, test, docs, sync, install, contract, or runtime evidence.
Output Format
Return a compact table with:
- path or pattern
- bucket
- why it exists
- evidence command
- recommendation: keep, commit, ignore, regenerate, inspect again, or cleanup candidate
- risk if deleted
End with a short "do not delete yet" list for any file whose role is uncertain.
Boundaries
- Do not auto-write canonical state without Warden approval.
- Keep one-run task details in workerTaskPackets, not durable identity.
- Do not delete files as part of inventory classification unless the user separately approves a cleanup action.
- Do not treat runtime mirrors or generated reports as source of truth when canonical or config sources exist.
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.
- 13d ago First seen · 99 lines · 45 tokens per session scan A f56225c64786
same-set-reusable-flow-for-project-file-inventor is a skill published in the GitHub repository KimYx0207/Meta_Kim (273 stars, last pushed 3d ago), licensed Apache-2.0. It adds 45 tokens to every session and 1,143 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
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
chinese-documentation
A Chinese technical-documentation style guide covering spacing, punctuation, numbers, terminology, and links when Chinese and English appear together.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
ijfw-workflow
Use when the user says: 'build', 'create', 'plan', 'new project', 'brainstorm', 'design', 'UI', 'website', 'dashboard', 'app', 'help me build', 'launch', 'book', 'campaign', or anything project-level. Skill body decides Quick vs Deep path.
ijfw-plan
Use when the user says 'plan this', 'plan it', 'make a plan', 'let's plan', 'draft a plan', 'how should we tackle this', 'break this down', or invokes '/ijfw-plan'. Produces a falsifiable PLAN.md (software, book, campaign, design, research) with task breakdown, dependency wave-table, and success criteria — gated by…
ijfw-writing-skills
Authoring discipline for new IJFW skills. Use when creating a new skill, writing a skill, making a skill that does X, or asked to add a skill. Trigger: create a new skill, write a skill, new skill, make me a skill, skill that does, /ijfw-writing-skills.