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 wahidyankf/ose-public --skill docs-managing-file-operationsgit clone --depth 1 https://github.com/wahidyankf/ose-publicWrote 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/wahidyankf/ose-public/docs-managing-file-operations)<a href="https://agentmods.dev/skills/wahidyankf/ose-public/docs-managing-file-operations"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/docs-managing-file-operations/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/wahidyankf/ose-public/docs-managing-file-operations"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/docs-managing-file-operations.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.00071 | $0.00556 |
| Opus 5.5 | $0.00028 | $0.00222 |
| Sonnet 5.5 | $0.00014 | $0.00111 |
| Haiku 4.5 | $0.00007 | $0.00056 |
Grade A, and why
docs-managing-file-operations 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 2d 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation: Managing File Operations
Methodology for safely managing files and directories in docs/ while maintaining kebab-case
conventions, fixing links, preserving git history, and avoiding orphaned references.
Reference Modules
- When to Use and Naming Convention — when to use this agent, what it's not for, and the file naming convention review.
- Discovery and Planning — Phase 1-2 of the four-phase process: Discovery & Analysis, then Planning.
- Execution and Validation — Phase 3-4 of the four-phase process: Execution, then Validation.
- Deletion Operations — safe deletion, deleting directories, the deletion safety checklist.
- Link Updates and Git Operations — calculating relative paths, removing links to deleted files, git best practices, batch ordering.
- Index Updates and Validation — when/how to update README.md indices, the full validation checklist.
- Safety Guidelines and Edge Cases — read-before-edit, confirmation gates, README.md special-casing, circular updates, uncommitted files.
- Integration and Communication —
coordinating with
docs-link-checker/rules-checker/docs-maker, summary format, and the anti-patterns table.
Core Principles
git mv/git rmalways, nevermv/rm— history preservation is non-negotiable.- Find every reference before deleting — an unlinked file is an orphan; a deleted file with surviving links is a 404.
- Plan, confirm, then execute — large reorganizations get a presented plan and explicit user confirmation before Phase 3 touches anything.
Related Skills
docs-validating-links,docs-applying-content-quality,docs-applying-diataxis-framework,repo-practicing-trunk-based-development.
What ships with it
10 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.
- README.md 575 B
- reference/deletion-operations.md 1.7 KB
- reference/discovery-and-planning.md 2.0 KB
- reference/execution-and-validation.md 1.4 KB
- reference/index-updates-and-validation.md 2.1 KB
- reference/integration-communication-antipatterns.md 3.3 KB
- reference/link-updates-and-git-ops.md 2.0 KB
- reference/README.md 1.1 KB
- reference/safety-and-edge-cases.md 2.2 KB
- reference/when-to-use-and-naming.md 2.4 KB
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.
- 2d ago First seen · 43 lines · 71 tokens per session scan A 274837fd9284
docs-managing-file-operations is a skill published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 71 tokens to every session and 556 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-14.
Other skills, from other repositories
upgrade-packages-js
Safely upgrade JavaScript packages with breaking change detection, migration guidance, and automated code migrations (npm/pnpm/yarn). Cross-platform with git safety branch enforcement.
sync
Sync the current session branch with its upstream branch, or publish the current session branch to a remote. Use when the user asks to sync a branch, pull latest changes, rebase onto upstream, push current branch, publish branch, or set upstream.
merge
Merge changes from the topic branch to the merge base branch. Use when the user wants to merge their session's work back to the base branch.
publish-npm-version
Cuts the next release of Prisma 8: bumps the root package.json version (on the v8 RC line: 8.0.0-rc.N → rc.N+1), propagates it to every workspace package, and opens a PR titled "chore(release): bump to ". When the maintainer merges the PR, the Publish to npm workflow runs automatically and ships the new version to npm…
contrib-pr
Open a high-quality external contributor PR against prisma/orm. Use when the user is an outside contributor (not a Prisma maintainer) and wants to submit a change as a pull request from a fork. Encodes the contribution flow from CONTRIBUTING.md so the resulting PR passes review on the first round.
update-pr
Update the pull request for the current session. Use when the user wants to push new changes to an existing PR.