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 1mancompany/OneManCompany --skill tool_managementgit clone --depth 1 https://github.com/1mancompany/OneManCompanyWrote 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/1mancompany/onemancompany/tool_management)<a href="https://agentmods.dev/skills/1mancompany/onemancompany/tool_management"><img src="https://agentmods.dev/badge/skills/1mancompany/onemancompany/tool_management/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/1mancompany/onemancompany/tool_management"><img src="https://agentmods.dev/badge/skills/1mancompany/onemancompany/tool_management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00000 | $0.00163 |
| Opus 5 | $0.00000 | $0.00081 |
| Sonnet 5 | $0.00000 | $0.00033 |
| Haiku 4.5 | $0.00000 | $0.00016 |
Grade A, and why
tool_management 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.
What it actually says
Tool Management — Tool Management Capability
Responsibilities
- Evaluate and introduce tools and systems needed by the company
- Manage usage and maintenance of existing tools
- Ensure integration and interoperability between tools
Tool Evaluation Criteria
- Whether it addresses actual business needs
- Learning curve and ease of adoption
- Scalability and maintenance cost
- Compatibility with the existing tech stack
Operating Methods
- Use
add_office_tool(name, description)to register new tools - Use
list_current_tools()to view the current tool inventory - Each tool is displayed as equipment in the pixel art office
Naming Conventions
- Tool names should be concise and clear (e.g., "CI/CD Pipeline", "Code Linter")
- Descriptions should explain the tool's specific purpose and value
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 · 22 lines · 0 tokens per session scan A 6be37e47582f
tool_management is a skill published in the GitHub repository 1mancompany/OneManCompany (415 stars, last pushed 15d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 163 tokens. 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
tmux
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
cron
Schedule reminders and recurring tasks.
welcome
Introduce yourself to a newly connected channel. Triggered automatically when a channel is first wired. Send a friendly greeting and brief overview of what you can do.
add-teams
Add Microsoft Teams channel integration via Chat SDK.
meeting-note-summarizer
Turn meeting notes or transcripts into factual summaries, decisions, questions, and action items. Use when a user wants a concise recap or needs explicit owners and deadlines extracted without filling in missing details.
daily-standup-journal
Generate concise daily standups, reflection prompts, and weekly retrospectives for individuals or teams. Use for planning a day, surfacing blockers, reviewing user-provided entries, or drafting a check-in without assuming prior history.