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 calvinchengx/data-agent-service --skill result-presentationgit clone --depth 1 https://github.com/calvinchengx/data-agent-serviceWrote 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/calvinchengx/data-agent-service/result-presentation)<a href="https://agentmods.dev/skills/calvinchengx/data-agent-service/result-presentation"><img src="https://agentmods.dev/badge/skills/calvinchengx/data-agent-service/result-presentation.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.00023 | $0.00460 |
| Opus 5 | $0.00012 | $0.00230 |
| Sonnet 5 | $0.00005 | $0.00092 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
result-presentation 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 7d 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
Every answer has four parts, in this order. Leave one out and the answer cannot be verified.
- The figure, with its unit and period. A count is "n"; a money amount carries the currency the catalog gave; a rate is a percentage to one decimal unless the catalog's
unitOfMeasurementsays otherwise; a duration carries its unit. Round to what the question needs, not to what the database returned. - The definition you applied, named inline: the glossary term or metric, and the exclusion or convention that changed the number ("… — excluding X, per the glossary"). If you chose between two catalog definitions, say which and why in one clause.
- Where it came from: the table(s) the executor reported in
tables. One clause, no path. - A caveat only when the catalog raised one or the result envelope flagged it: a nullable column you treated a particular way,
truncated: true, a period the data does not fully cover, a column the access rules withheld (and therefore a figure that excludes it).
Shape
- One figure → one sentence leading with it.
- Several rows → a short table (≤ 20 rows) with the measure as the last column and the ordering the question implies ("fastest" → ascending on the measure). Name the measure column by its glossary term, not the SQL alias.
- A comparison → both figures and the difference, in the unit, once.
Never
- a figure with no query behind it in this conversation;
- "approximately" for a number you computed exactly;
- the SQL itself, unless asked — the definition is the explanation, the SQL is the evidence, and the evidence is recorded;
- an apology, a preamble, or a description of what you are about to do.
Abstentions and refusals
An abstention is one or two sentences: what the question needs, which catalog terms you searched, what is absent. A refusal is one sentence: what was withheld and that the executor, not you, decides access.
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.
- 7d ago First seen · 30 lines · 23 tokens per session scan A 537a479f794c
result-presentation is a skill published in the GitHub repository calvinchengx/data-agent-service (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 23 tokens to every session and 460 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
azure-ad-illicit-consent-grant
Exploit Illicit Consent Grants in Azure Active Directory (Entra ID). This skill covers crafting a malicious OAuth application to trick victims into granting broad permissions (like reading emails, modifying files) without requiring their password or MFA.
code-changes
Orchestration workflow for any task that ends in code changes: issue analysis, pull request review, feature implementation, bug fixes, refactors, or fleshing out an idea. MUST be invoked at the start of such a task, before reading or writing any code. Defines how to analyze first, gate on user approval, plan, pick the…
auditing-azure-active-directory-configuration
Auditing Microsoft Entra ID (Azure Active Directory) configuration to identify risky authentication policies, overly permissive role assignments, stale accounts, conditional access gaps, and guest user risks using AzureAD PowerShell, Microsoft Graph API, and ScoutSuite.
detecting-azure-service-principal-abuse
Detect and investigate Azure service principal abuse including privilege escalation, credential compromise, admin consent bypass, and unauthorized enumeration in Microsoft Entra ID environments.
detecting-azure-lateral-movement
Detect lateral movement in Azure AD/Entra ID environments using Microsoft Graph API audit logs, Azure Sentinel KQL hunting queries, and sign-in anomaly correlation to identify privilege escalation, token theft, and cross-tenant pivoting.
remotion-animation
Generates animation configurations for Remotion including spring configs, interpolations, easing functions, and timing logic. Focuses ONLY on animation parameters, NOT component implementation. Use when defining animation behavior or when asked to "configure animations", "setup spring configs", "define easing curves".