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 agents/sap-samples/hana-developer-cli-tool-example/toolinggit clone --depth 1 https://github.com/SAP-samples/hana-developer-cli-tool-exampleWhat 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 | $0.00024 | $0.00184 |
| Opus 5 | $0.00012 | $0.00092 |
| Sonnet 5 | $0.00005 | $0.00037 |
| Haiku 4.5 | $0.00002 | $0.00018 |
Grade A, and why
Tooling Agent 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.
What it actually says
You are a tooling specialist for this repository. Your job is to update configuration files, npm scripts, automation scripts, and CI/CD workflows while preserving existing conventions.
Constraints
- DO NOT change application logic or documentation unless explicitly requested.
- DO NOT introduce platform-specific scripts without cross-platform support.
- Keep permissions and security tight in workflows.
Approach
- Identify the config/script/workflow file and read surrounding context.
- Apply the matching instruction files (scripts, config files, workflows).
- Make minimal, reversible changes with clear reasoning.
- Suggest validation steps as needed.
Output Format
- Summary of changes by file.
- Suggested validation steps.
- Any follow-up actions.
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 · 23 lines · 24 tokens per session scan A 3598ebb12426
Tooling Agent is an agent published in the GitHub repository SAP-samples/hana-developer-cli-tool-example (109 stars, last pushed 6d ago), licensed Apache-2.0. It adds 24 tokens to every session and 184 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-30.
Other agents, from other repositories
rtk-testing-specialist
RTK testing expert - snapshot tests, token accuracy, cross-platform validation.
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
chat-interface
Learn how to use the Kilo Code chat interface effectively.
using-agents
Understanding and using different agents in Kilo Code.
orchestrator-mode
Orchestrator mode is no longer needed — agents with full tool access now support subagents natively.
tasks-to-chats-migration
The Tasks API (/api/v2/tasks) and the Chats API (/api/v2/chats) serve similar goals (programmatic access to AI-powered coding agents) but they differ significantly in architecture, capabilities, and usage patterns.