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 agentmods add skills/sachinshelke/toolsconnector/documenternpx skills add sachinshelke/ToolsConnector --skill documentergit clone --depth 1 https://github.com/sachinshelke/ToolsConnectorWrote 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/sachinshelke/toolsconnector/documenter)<a href="https://agentmods.dev/skills/sachinshelke/toolsconnector/documenter"><img src="https://agentmods.dev/badge/skills/sachinshelke/toolsconnector/documenter.svg" alt="Measured on agentmods" 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.00010 | $0.00209 |
| Opus 5 | $0.00005 | $0.00105 |
| Sonnet 5 | $0.00002 | $0.00042 |
| Haiku 4.5 | $0.00001 | $0.00021 |
Grade A, and why
documenter 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 5d 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
Documenter Persona
Overview
You write and maintain all documentation for ToolsConnector — README, quickstart guides, API references, connector authoring tutorials, architecture docs, and CONTRIBUTING.md.
Rules
- Accuracy: Documentation MUST reflect current code. Read source files before writing docs.
- Runnable Examples: All code examples must be copy-pasteable and functional.
- Dual Usage: Always show both sync and async usage patterns.
- No Speculation: NEVER document unimplemented features or planned functionality.
- Changelog: Update CHANGELOG.md with every significant change.
- Google Style: Follow the same docstring conventions used in the code.
Execution Workflow
- Read the source code for the module being documented.
- Write documentation that explains what it does, how to use it, and common patterns.
- Include code examples that actually work.
- Cross-reference related modules where helpful.
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.
- 5d ago First seen · 23 lines · 10 tokens per session scan A 69a6ab374d16
documenter is a skill published in the GitHub repository sachinshelke/ToolsConnector (5 stars, last pushed 5d ago), licensed Apache-2.0. It adds 10 tokens to every session and 209 once invoked, about $0.0001 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-31.
Other skills, from other repositories
add-test
Use when adding unit or integration tests. Provides test patterns, naming conventions, and fixtures for Python (pytest), TypeScript (vitest), Java (JUnit/Mockito), and Rust.
validate-docs
Use when reviewing or validating documentation. Checks for clarity, completeness, broken links, undefined terms, and ensures beginners can follow guides without prior knowledge of the SDK.
debug-ci
Use when CI/CD pipeline fails. Provides systematic diagnosis for lint, type, test, and build failures across Python, TypeScript, Java, Rust, and n8n SDKs.
add-sdk-method
Use when adding a new method, function, or API endpoint to the SDK. Ensures consistent implementation across all SDKs (Python, TypeScript, Java, Rust CLI) with proper types, tests, and naming conventions.
run-integration
Use when running integration tests against a real Metadata instance. Guides setup of environment variables (AISDKHOST, AISDKTOKEN) and runs tests that make actual API calls.
dignified-python
Load ONLY for Python code Use when writing, reviewing, or refactoring Python to ensure adherence to LBYL exception handling patterns, modern type syntax (list[str], str | None), pathlib operations, ABC-based interfaces, absolute imports, and explicit error boundaries at CLI level. Also provides production-tested code…