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 ChronoAIProject/NyxID --skill fallback-to-calling-agentgit clone --depth 1 https://github.com/ChronoAIProject/NyxIDWrote 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/chronoaiproject/nyxid/fallback-to-calling-agent)<a href="https://agentmods.dev/skills/chronoaiproject/nyxid/fallback-to-calling-agent"><img src="https://agentmods.dev/badge/skills/chronoaiproject/nyxid/fallback-to-calling-agent.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00119 | $0.01105 |
| Opus 5 | $0.00060 | $0.00553 |
| Sonnet 5 | $0.00024 | $0.00221 |
| Haiku 4.5 | $0.00012 | $0.00111 |
Grade A, and why
fallback-to-calling-agent 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 8d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fallback: hand an unsolvable request back to your caller
You are running as a model invoked by another agent — your "caller". The caller can act in an environment you do not have: typically a local workspace with files, a shell, and direct tools. Your job here is the catch half of a try-catch around your own work. When you genuinely cannot finish a request with the capabilities available to you server-side, you do not fail silently, apologize into a dead end, or fabricate a result. You return the original problem to your caller — cleanly and completely — so it can finish the job.
When this applies (the catch)
First, actually try. This fallback is for genuine dead ends, not an excuse to punt. Before handing back, make a real attempt with what you have: look for a matching skill, workflow, connector, or tool, and use it.
Hand the request back when any of these is true after that honest attempt:
- No capability exists — there is no server-side skill, workflow, connector, or tool that can do what is being asked.
- An attempt failed terminally — you tried the available path and it returned an unrecoverable error (missing connector, tool error, failed run) with no viable alternative.
- It inherently needs the caller's environment — the task requires acting on the caller's local files, running code or commands locally, or local context you cannot see. This is the strongest reason to delegate: the caller can do it and you structurally cannot.
Do not hand back merely because you are slightly unsure of a normal answer you could give. The fallback is for "cannot", not for "not perfectly confident".
What to return (the handoff)
Return a single, clearly-marked handoff. Keep the user's original request verbatim — do not paraphrase away detail. Include just enough context that the caller can act immediately without re-deriving anything, and never more than needed.
Structure it like this (plain text the caller can read and act on):
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.
- 8d ago First seen · 91 lines · 119 tokens per session scan A c4133108aead
fallback-to-calling-agent is a skill published in the GitHub repository ChronoAIProject/NyxID (36 stars, last pushed today), licensed Apache-2.0. It adds 119 tokens to every session and 1,105 once invoked, about $0.0006 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-30.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
ue-mcp-epic-routing
Use when deciding between ue-mcp's native category actions and Epic's wrapped ToolsetRegistry tools (the epic actions, incl. the Blueprint graph DSL) for a task in Unreal. Pulls in when authoring Blueprint graph bodies, or any time both a native action and an epic action could do the job and you need to pick.
mcp-google-map-project
Project knowledge for developing and maintaining @cablate/mcp-google-map. Architecture, Google Maps API guide, GIS domain knowledge, and design decisions. Read this skill to onboard onto the project or make informed development decisions.
frontmcp-setup
Use when starting, scaffolding, or organizing a FrontMCP project. Covers creating a new project (CLI scaffold or manual) for Node, Vercel, and other targets; standalone versus Nx-monorepo layout, naming conventions, generators, and dependency rules; composing multiple @App classes, ESM packages, and remote MCP servers…
authoring-decorators
Use when the user wants to write a new prompt decorator - either a personal one for their repo or a contribution back to the upstream catalogue. Walks through the JSON schema, the extensions/ convention, how to verify a new decorator end-to-end through the hook, and how to diagnose failures using debug logging and…