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 commands/xi-kari/crossframe-skill/crossframe-inquirygit clone --depth 1 https://github.com/xi-kari/crossframe-skillWrote 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/commands/xi-kari/crossframe-skill/crossframe-inquiry)<a href="https://agentmods.dev/commands/xi-kari/crossframe-skill/crossframe-inquiry"><img src="https://agentmods.dev/badge/commands/xi-kari/crossframe-skill/crossframe-inquiry.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.00103 |
| Opus 5 | $0.00000 | $0.00051 |
| Sonnet 5 | $0.00000 | $0.00021 |
| Haiku 4.5 | $0.00000 | $0.00010 |
Grade A, and why
crossframe-inquiry 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 5d 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
/crossframe-inquiry
Use CrossFrame Inquiry after a completed CrossFrame diagnosis, article, review, or suite workflow when the user wants follow-up questions, counterexamples, missing evidence, transfer conditions, or action boundaries.
This explicit command is allowed when prior CrossFrame output exists. Read skills/crossframe-inquiry/SKILL.md, then follow its routed instructions. Treat inquiry as a post-completion follow-up layer, not a new diagnosis upgrade.
User input:
$ARGUMENTS
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.
- 5d ago First seen · 10 lines · 0 tokens per session scan A 140e17500897
crossframe-inquiry is a command published in the GitHub repository xi-kari/crossframe-skill (18 stars, last pushed 29d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 103 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-30.
Other commands, from other repositories
init
Initialize configurations for Supabase local development.
secrets
Provides tools for managing environment variables and secrets for your Supabase project.
stop
Stops the Supabase local development stack.
network-bans
Network bans are IPs that get temporarily blocked if their traffic pattern looks abusive (e.g. multiple failed auth attempts).
prep
Prepare the meeting. One page from the record.
receipts
Find the receipt. A dated line, or it did not happen.