Borrowing it
Nothing to install: this file belongs to kridaydave/File-Organizer-MCP. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kridaydave/File-Organizer-MCP/main/.opencode/skills/verify-file-organizer/SKILL.mdgit clone --depth 1 https://github.com/kridaydave/File-Organizer-MCPWrote 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/kridaydave/file-organizer-mcp/verify-file-organizer)<a href="https://agentmods.dev/skills/kridaydave/file-organizer-mcp/verify-file-organizer"><img src="https://agentmods.dev/badge/skills/kridaydave/file-organizer-mcp/verify-file-organizer/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/kridaydave/file-organizer-mcp/verify-file-organizer"><img src="https://agentmods.dev/badge/skills/kridaydave/file-organizer-mcp/verify-file-organizer.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.00087 | $0.02069 |
| Opus 5.5 | $0.00035 | $0.00828 |
| Sonnet 5.5 | $0.00017 | $0.00414 |
| Haiku 4.5 | $0.00009 | $0.00207 |
Grade A, and why
verify-file-organizer 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 15d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify File Organizer
The unit tests call handlers directly. They do not prove the server answers a JSON-RPC handshake, that a tool is reachable by name, or that a move lands on disk and undo puts it back. This skill drives the built server the way a client does and reads the result off the filesystem.
Everything runs inside a throwaway sandbox under the OS temp directory. Your real
config.json, operations.jsonl, rollbacks and backups are never read or
written. Do not point this at a real home directory to "just check quickly".
The helper
scripts/control-file-organizer.mjs is the harness. Run it from the repo root.
Every subcommand prints JSON on stdout and keeps stdout free of diagnostics.
C=.opencode/skills/verify-file-organizer/scripts/control-file-organizer.mjs
node $C doctor # is this instance worth driving?
node $C tools # every registered tool, one line each
node $C tools --filter organize
node $C schema organize_files # input schema plus honest annotations
node $C sandbox --fresh # recreate fixtures, print the paths
node $C call <tool> --arg k=v --json
node $C history # operations.jsonl written by this sandbox
node $C cleanup # remove the sandbox
Exit code is 0 when the tool call succeeded, 1 when the tool returned an error, 2 when the harness itself could not run.
Flags
| Flag | Effect |
|---|---|
--sandbox <path> |
Use a specific sandbox root instead of the default. |
--fresh |
Recreate the sandbox and its fixtures. Refuses on any directory this helper did not create. |
--arg key=value |
A tool argument. Repeatable. Values coerce true, false, null, numbers, and JSON. |
--json |
Force response_format=json and pretty-print the parsed body. |
--out <file> |
Also write the full result to a file as proof. Cleanup never deletes it. |
--verbose |
Echo server stderr. Use this when a call fails for no visible reason. |
A bare --key value pair works too, so --dry_run false and --dry_run=false
both send a tool argument. Where both forms set the same key, --arg wins,
because it is the explicit one.
What ships with it
12 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.
- references/features/customize.md 3.1 KB
- references/features/discover.md 2.1 KB
- references/features/duplicates.md 2.7 KB
- references/features/find.md 3.3 KB
- references/features/inspect.md 3.1 KB
- references/features/organize.md 5.1 KB
- references/features/README.md 5.0 KB
- references/features/rename.md 1.5 KB
- references/features/rollback.md 5.6 KB
- references/features/security.md 5.3 KB
- references/features/watch.md 3.3 KB
- scripts/control-file-organizer.mjs 20 KB runs code
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.
- 15d ago Changed · +4 lines a1292f597adb
- 18d ago Changed · +11 lines d524b77661b1
- 24d ago Changed · -1 tokens per session 5889977e9a64
- 25d ago First seen · 174 lines · 88 tokens per session scan A 86f259bff780
verify-file-organizer is a skill published in the GitHub repository kridaydave/File-Organizer-MCP (46 stars, last pushed 5d ago), licensed MIT. It adds 87 tokens to every session and 2,069 once invoked, about $0.0003 per session on Opus 5.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-10-05.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
observability-langsmith
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
reenable-test
Guide for investigating, fixing, verifying via TDD, and re-enabling disabled or flaky Chromium tests (C++, Android Java, or WebUI). Use this skill when asked to deflake, fix, or re-enable a disabled or flaky test case, or to verify post-submit stability of a re-enabled test. Don't use for disabling a failing test…
experimental-code-coverage-local-debugger
Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.