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/soliantconsulting/claris-docs/filemaker-servernpx skills add soliantconsulting/claris-docs --skill filemaker-servergit clone --depth 1 https://github.com/soliantconsulting/claris-docsWhat 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.00103 | $0.00545 |
| Opus 5 | $0.00051 | $0.00272 |
| Sonnet 5 | $0.00021 | $0.00109 |
| Haiku 4.5 | $0.00010 | $0.00055 |
Grade A, and why
filemaker-server 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claris FileMaker Server Help
Navigator skill — routes to reference files, then fetches live Claris documentation on demand.
FileMaker Server hosts FileMaker databases for multi-user access, providing the Admin Console, scheduling, backups, web publishing, ODBC/JDBC sharing, and AI model hosting.
How to use this skill
- Identify the topic area below that matches the user's question.
- Read the corresponding
references/file to find the relevant page URL(s). - Fetch the page with
WebFetchfrom the URL listed there. - If a fetch returns 404, tell the user the page may have moved and suggest running
update.pyto refresh references.
Topic areas
Admin Console & settings
Startup, general settings, server info, licensing, Admin Console access, clients, command line interface.
→ references/server-admin-settings.md
Databases & hosting
Hosting databases, uploading, verifying, opening/closing/pausing files, web publishing settings, ODBC/JDBC, container data.
→ references/server-databases-hosting.md
Backups & schedules
Backup options, creating schedules, schedule types, restoring, saving/loading schedule settings.
→ references/server-backups-schedules.md
Monitoring & logs
Dashboard, system overview, log files (access, event, client stats, server stats, API logs), Event Viewer.
→ references/server-monitoring-logs.md
Security & authentication
SSL certificates, Let's Encrypt, external authentication, OAuth, permissions, restricting access.
→ references/server-security.md
AI services
Configuring AI services, creating API keys, downloading models, fine-tuning, enabling the model server.
→ references/server-ai.md
Troubleshooting & maintenance
General/network/client problems, Admin Console issues, performance, plug-ins, testing, uninstall.
→ references/server-troubleshooting.md
Installation & configuration
→ references/server-installation.md
Network install setup
→ references/server-network-install.md
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- evals/evals.json 1.3 KB
- references/server-admin-settings.md 7.7 KB
- references/server-ai.md 1.3 KB
- references/server-backups-schedules.md 3.9 KB
- references/server-databases-hosting.md 4.7 KB
- references/server-installation.md 14 KB
- references/server-monitoring-logs.md 3.4 KB
- references/server-network-install.md 2.1 KB
- references/server-release-notes.md 254 B
- references/server-security.md 1.8 KB
- references/server-troubleshooting.md 1.9 KB
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 · 64 lines · 103 tokens per session scan A d691bd29ef4f
filemaker-server is a skill published in the GitHub repository soliantconsulting/claris-docs (10 stars, last pushed 9d ago), licensed MIT. It adds 103 tokens to every session and 545 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.