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/choria-io/fisk-ai/toolsgit clone --depth 1 https://github.com/choria-io/fisk-aiWrote 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/choria-io/fisk-ai/tools)<a href="https://agentmods.dev/agents/choria-io/fisk-ai/tools"><img src="https://agentmods.dev/badge/agents/choria-io/fisk-ai/tools.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 | $0.00000 | $0.01945 |
| Opus 5 | $0.00000 | $0.00972 |
| Sonnet 5 | $0.00000 | $0.00389 |
| Haiku 4.5 | $0.00000 | $0.00194 |
Grade A, and why
tools 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 3d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
+++ title = "Tool selection" description = "which commands become tools, and the tags fisk interprets" toc = true weight = 30 +++
Run the fisk info command to verify what tools the agent has access to:
$ fisk info
╭───────────────────┬────────┬───────────────────────────────────────────────────────┬──────╮
│ TOOL │ SOURCE │ DESCRIPTION │ TAGS │
├───────────────────┼────────┼───────────────────────────────────────────────────────┼──────┤
│ say │ local │ Say something using the configured command │ │
│ think │ local │ Think something using a cow │ │
│ ask_human_confirm │ local │ Ask the human operator a yes/no question at the te... │ │
│ ask_human_select │ local │ Ask the human operator to choose one option from a... │ │
│ ask_human_input │ local │ Ask the human operator to type a free-text value a... │ │
╰───────────────────┴────────┴───────────────────────────────────────────────────────┴──────╯
Prompt:
Tell short jokes using Cows!
...
The output shows the say and think tools and some Human in the Loop tools. When the configuration sets a model,
fisk info also prints a Model section first, listing the resolved model and provider, whether thinking is enabled,
and how tool search will behave, so you can confirm the backend and feature gates without starting a run.
Application tags
The application can declare that the LLM never gets the think tool:
- name: think
description: Think something using a cow
type: exec
tags: [ ai:deny ]
# ...
Adding the ai:deny tag to a command means Fisk AI never exposes that tool to the LLM. fisk info confirms the LLM
only gets the say tool now.
Agent configuration
The agent.yaml can also include only certain tools:
include:
tools:
- ^say
Or exclude certain tools specifically:
exclude:
tools:
- ^think
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.
- 3d ago First seen · 175 lines · 0 tokens per session scan A 86da63a286da
tools is an agent published in the GitHub repository choria-io/fisk-ai (5 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,945 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-31.
Other agents, from other repositories
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.