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 sandbaseai/sandbase-skills --skill call-prepgit clone --depth 1 https://github.com/sandbaseai/sandbase-skillsWrote 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/sandbaseai/sandbase-skills/call-prep)<a href="https://agentmods.dev/skills/sandbaseai/sandbase-skills/call-prep"><img src="https://agentmods.dev/badge/skills/sandbaseai/sandbase-skills/call-prep/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/sandbaseai/sandbase-skills/call-prep"><img src="https://agentmods.dev/badge/skills/sandbaseai/sandbase-skills/call-prep.svg" alt="Reviewed on agentmods" width="80" 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.00037 | $0.00608 |
| Opus 5.5 | $0.00015 | $0.00243 |
| Sonnet 5.5 | $0.00007 | $0.00122 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade A, and why
call-prep 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 1mo 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Call Prep
Use this Skill to produce a bounded, verifiable Call Prep outcome. Preserve the user's chosen stack, source material, and authorization boundaries.
Read the SandBase API map only when the task genuinely needs an external data source or generative model.
Workflow
- Inspect the available files, runtime, versions, inputs, and existing conventions before deciding what to change.
- Restate the requested outcome, constraints, acceptance checks, and any assumption that could change the result.
- Produce the smallest complete implementation, analysis, or artifact that satisfies those checks.
- Verify the real output with appropriate tests, previews, calculations, or source comparison; do not infer success from file creation alone.
- Return the deliverable, evidence of validation, material assumptions, and unresolved limitations.
Quality gates
- State the objective, decision owner, horizon, inputs, constraints, and definitions before analyzing.
- Show formulas, assumptions, ranges, and scenarios so another reviewer can reproduce the conclusion.
- Separate observations, judgments, actions, owners, and dates; escalate legal, tax, accounting, or policy ambiguity.
Focus checks
- Confirm the call objective, attendees, account context, known sensitivities, evidence-backed hypotheses, agenda, and questions; clearly mark anything that remains unverified.
SandBase boundary
Keep the core Call Prep work local. Use SandBase only for current external evidence, search, scraping, enrichment, or model inference that is not already available through the user's authorized tools.
- Call
sandbase_discoverwith a short capability query. - Call
sandbase_inspectfor viable candidates and compare the live schema, coverage, limits, output, execution mode, and price. - Prefer a dedicated tool or API the user already has. Send only the minimum necessary data.
- Before any paid call, show the endpoint, important arguments, current unit price, call count, and total estimate or uncertainty, then obtain confirmation.
- Use
sandbase_accountbefore an approved multi-call batch and callsandbase_runonly with current schema-defined arguments. - Poll asynchronous work with
sandbase_run_getusing the same run ID; never resubmit merely because it is pending. - Use
sandbase_runsonly to recover status or reconcile observed cost.
What ships with it
1 file 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.
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.
- 1mo ago First seen · 47 lines · 37 tokens per session scan A a8e7b5eaf76c
call-prep is a skill published in the GitHub repository sandbaseai/sandbase-skills (203 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 37 tokens to every session and 608 once invoked, about $0.0001 per session on Opus 5.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-09-27.
Other skills, from other repositories
recruit-init
Uma habilidade que prepara um espaço de trabalho para recrutamento, com pastas, documentos de referência, registros e instruções para agentes de programação. Ela verifica dependências como Node.js, ferramentas de vagas e, opcionalmente, o Feishu.
mitiq-error-mitigation
A local experiment runner for testing four ways to reduce errors in sampled quantum circuits: zero-noise extrapolation, readout correction, probabilistic error cancellation, and Clifford data regression. It compares noisy and mitigated results under the same sampling budget.
quantum-ground-state
A narrowly defined quantum solver for the ground-state energy of a two-quantum-bit Pauli Hamiltonian in a specified one-excitation sector. It uses a noiseless statevector VQE and checks the result against an exact calculation; VQE is a method that searches for a low-energy quantum state.
randomized-measurements
A small quantum-state measurement tool that estimates the purity of a selected group of qubits using random measurements, then compares the estimate with an exact value. It supports 2–6 qubits and product or GHZ states.
quantum-hidden-shift
A quantum-circuit implementation of the hidden-shift problem for even-sized quadratic bent functions. The problem hides a bit string that shifts one function relative to another, and the circuit is designed to recover that shift.
quantum-lcu
A quantum-computing skill for explaining, running, and modifying the linear-combination-of-unitaries method with Qiskit. This method combines several unitary quantum operations using given coefficients and an initial state.