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 QVerisAI/open-qveris-skills --skill qveris-supply-chain-catalyst-radargit clone --depth 1 https://github.com/QVerisAI/open-qveris-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/qverisai/open-qveris-skills/qveris-supply-chain-catalyst-radar)<a href="https://agentmods.dev/skills/qverisai/open-qveris-skills/qveris-supply-chain-catalyst-radar"><img src="https://agentmods.dev/badge/skills/qverisai/open-qveris-skills/qveris-supply-chain-catalyst-radar/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/qverisai/open-qveris-skills/qveris-supply-chain-catalyst-radar"><img src="https://agentmods.dev/badge/skills/qverisai/open-qveris-skills/qveris-supply-chain-catalyst-radar.svg" alt="Reviewed on agentmods" width="80" 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.00094 | $0.01551 |
| Opus 5 | $0.00047 | $0.00776 |
| Sonnet 5 | $0.00019 | $0.00310 |
| Haiku 4.5 | $0.00009 | $0.00155 |
Grade A, and why
qveris-supply-chain-catalyst-radar 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 12d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QVeris Supply Chain Catalyst Radar
Produce an evidence-first company catalyst report adapted from MarketBot's catalyst, logic-chain, and thesis-tracking workflows. Use only standardized qveris_finance.* CAPs; never call upstream data sources or raw provider routes.
Execute In Five Gates
1. Fix Identity And Scope
- Require a ticker or market-qualified security code. Normalize unambiguous A-share codes; reject company-name guesses and ambiguous exchanges.
- Select one workflow:
company_radar: issuer identity plus supply-chain relationships, with optional ALT corroboration.hiring_innovation: identity, job postings, and patents.contract_watch: identity, government contracts, and regulatory filings.shipping_watch: identity, supply-chain relationships, and one or more explicit public IMO/MMSI identifiers.
- Treat every vessel observation as independent of the issuer until an accepted relationship record explicitly links the same vessel identifier. Never send a ticker to
ALT.SHIPPING_AIS.
Complete this gate only when issuer, UTC window, workflow, and any vessel IDs are explicit.
2. Plan And Enforce Budget
Run the bundled planner before transport:
node qveris-supply-chain-catalyst-radar/scripts/supply_chain_workflow.mjs --workflow company_radar --issuer AAPL --lookback-days 90 --max-calls 8 --dry-run
max_calls counts observed capabilities/query attempts, including retries. Catalog/detail reads are control-plane operations. Required calls run first; optional jobs, patents, contracts, filings, news, and AIS calls run only when budget remains. If the required set does not fit, make zero data calls and return budget_limited.
Complete this gate only when the plan fits the hard budget or is explicitly budget-limited.
3. Execute Through The Shared Adapter
Prefer the bundled runner:
node qveris-supply-chain-catalyst-radar/scripts/supply_chain_workflow.mjs --workflow company_radar --issuer AAPL --lookback-days 90 --max-calls 8 --artifact report.observed-calls.json
What ships with it
16 files 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.
- agents/openai.yaml 269 B
- examples/default-markdown-report.md 829 B
- examples/live-e2e-output-2026-07-24.md 4.8 KB
- examples/live-e2e-output-2026-07-24.observed-calls.json 89 KB
- examples/natural-language-prompts.md 718 B
- fixtures/qveris/budget-limited-output.json 2.3 KB
- fixtures/qveris/fallback-output.json 2.4 KB
- fixtures/qveris/sample-output.json 2.8 KB
- references/qveris-retry-policy.md 878 B
- references/qveris-supply-chain-data-quality.md 2.3 KB
- references/qveris-tool-map.md 2.0 KB
- schemas/output.schema.json 7.0 KB
- scripts/supply_chain_evidence.mjs 13 KB runs code
- scripts/supply_chain_workflow.mjs 21 KB runs code
- tests/supply_chain_workflow.test.mjs 8.2 KB runs code
- THIRD_PARTY_NOTICES.md 600 B
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.
- 12d ago First seen · 136 lines · 94 tokens per session scan A 6c7521a37105
qveris-supply-chain-catalyst-radar is a skill published in the GitHub repository QVerisAI/open-qveris-skills (21 stars, last pushed 8d ago), licensed MIT. It adds 94 tokens to every session and 1,551 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…