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 om-context-nativegit 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/om-context-native)<a href="https://agentmods.dev/skills/calvinchengx/data-agent-service/om-context-native"><img src="https://agentmods.dev/badge/skills/calvinchengx/data-agent-service/om-context-native.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.00017 | $0.00244 |
| Opus 5 | $0.00009 | $0.00122 |
| Sonnet 5 | $0.00003 | $0.00049 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade A, and why
om-context-native 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 6d 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
Loaded when DAS_OM_CONTEXT_MODE=native and the catalog exposes find_context / get_asset_context. These replace steps 1–3 of om-grounded-sql; steps 4–6 and the abstention rules are unchanged.
- Call
find_contextonce with the question's business terms together, not one term at a time. It returns glossary terms, metrics, and candidate assets already related to each other. - Call
get_asset_contexton each asset you intend to query; it returns the table with its column descriptions, tags, keys, and linked terms in one payload. Still call the warehouse'sdescribe_table— the catalog describes meaning, the executor describes what is physically there, and the two can disagree (say so if they do). - A metric's
expressionis still the definition; the assembled context does not change that. - If
find_contextreturns nothing relevant, fall back tosearch_metadataper term before abstaining, and name both attempts in the abstention.
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.
- 6d ago First seen · 13 lines · 17 tokens per session scan A a0e2121eb588
om-context-native is a skill published in the GitHub repository calvinchengx/data-agent-service (0 stars, last pushed 4d ago), licensed Apache-2.0. It adds 17 tokens to every session and 244 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
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.
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.
Azure Identity Design
Entra ID, managed identity, and workload identity federation design for Azure — when to use which, and how to avoid long-lived service-principal secrets.
azure-ad-lateral-movement
Execute lateral movement within Microsoft Entra ID (formerly Azure AD) and Microsoft 365 environments. Use this skill to traverse cloud resources using compromised user tokens, managed identities, Primary Refresh Tokens (PRT), and application permissions (Service Principals) to achieve Global Administrator access.