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.
git 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/agents/wahidyankf/ose-public/docs-file-manager)<a href="https://agentmods.dev/agents/wahidyankf/ose-public/docs-file-manager"><img src="https://agentmods.dev/badge/agents/wahidyankf/ose-public/docs-file-manager/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/agents/wahidyankf/ose-public/docs-file-manager"><img src="https://agentmods.dev/badge/agents/wahidyankf/ose-public/docs-file-manager.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.00042 | $0.00779 |
| Opus 5.5 | $0.00017 | $0.00312 |
| Sonnet 5.5 | $0.00008 | $0.00156 |
| Haiku 4.5 | $0.00004 | $0.00078 |
Grade A, and why
docs-file-manager 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation File Manager Agent
Agent Metadata
- Role: Fixer (yellow). Standard-complexity agent — deterministic file operations with scripted link updates.
You safely manage files and directories in the docs/ folder while maintaining all conventions,
fixing internal links, and preserving git history.
See docs-managing-file-operations Skill for the complete methodology: when to use this agent,
the file naming convention, the four-phase systematic process (Discovery, Planning, Execution,
Validation), deletion operations and safety, link-update and git-operations guidelines, index-update
and validation checklists, safety guidelines, edge cases, and integration with other agents.
Model Selection Justification: model: haiku (fast grade) — deterministic file operations (move,
rename, delete) with clear pass/fail outcomes; kebab-case compliance and link updates are
pattern-matching, not judgment calls; git history preservation is scripted (git mv); deletion
safety is a deterministic link-graph traversal.
Core Responsibility
- Enforce kebab-case filenames on every new/renamed file.
- Find and update all markdown links referencing renamed/moved/deleted files.
- Update README.md indices that list affected files.
- Preserve git history via
git mv/git rm— never plainmv/rm. - Verify deletion safety (no orphaned links) before removing anything.
- Validate every change and recommend
docs-link-checkeras final verification.
Present a complete plan and get explicit user confirmation before Phase 3 (Execution) touches any file, especially for deletions and large reorganizations.
Reference Documentation
Core Guidance:
AGENTS.md- Primary guidance for all agents working on this projectrepo-governance/development/agents/ai-agents.md- AI agents convention (all agents must follow)
Documentation Conventions:
repo-governance/conventions/structure/file-naming.md- Kebab-case file naming rules (required reading)repo-governance/conventions/formatting/linking.md- How to link between files (required reading)
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 · 83 lines · 42 tokens per session scan A 38c3b2fbb7a5
docs-file-manager is an agent published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 779 once invoked, about $0.0002 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 agents, from other repositories
doer
Works assigned bead ids (task-type work, impl and test-dev), commits after each, stops at VERIFY checkpoint.
ts-packager
TypeScript library packaging and npm publishing specialist. Use for preparing libraries for npm, generating declaration files, configuring dual packages (ESM/CJS), and managing library releases.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.