Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add jaroslavsoucek-art/Giovanni/plugin install giovanniWrote 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/jaroslavsoucek-art/giovanni/market-radar)<a href="https://agentmods.dev/skills/jaroslavsoucek-art/giovanni/market-radar"><img src="https://agentmods.dev/badge/skills/jaroslavsoucek-art/giovanni/market-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/jaroslavsoucek-art/giovanni/market-radar"><img src="https://agentmods.dev/badge/skills/jaroslavsoucek-art/giovanni/market-radar.svg" alt="Reviewed on agentmods" width="80" 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.00032 | $0.02325 |
| Opus 5.5 | $0.00013 | $0.00930 |
| Sonnet 5.5 | $0.00006 | $0.00465 |
| Haiku 4.5 | $0.00003 | $0.00232 |
Grade A, and why
market-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 today.
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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/giovanni:market-radar
Run an external intelligence scan via the giovanni:market-radar agent. Strictly external sources (PR / LinkedIn / news / public roadmaps / vendor blogs) — separate from /giovanni:digest's internal signal pull. This command is a thin shell — scope, source rules, drift-against-settled-decisions logic live in the agent. This file is the invocation contract.
Usage
/giovanni:market-radar # default — periodic sweep, all markets × all layers
/giovanni:market-radar --focus <topic> # topic-focused, surface depth
/giovanni:market-radar --market <code> # single-market deep-dive
/giovanni:market-radar --market <code1>,<code2> # multi-market
/giovanni:market-radar --competitor <slug> # competitor deep-dive
/giovanni:market-radar --focus <topic> --market <code> # combined
/giovanni:market-radar --focus <topic> --horizon 90d # custom window
/giovanni:market-radar --focus <topic> --depth deep # multi-section analysis
Examples:
/giovanni:market-radar— periodic default sweep/giovanni:market-radar --focus regulatory-shift-X— cross-market regulatory scan, surface depth/giovanni:market-radar --focus regulatory-shift-X --market US,EU --horizon 90d --depth deep— US+EU regulatory deep-dive, 90 days/giovanni:market-radar --competitor <competitor-slug>— competitor-specific moves last 7 days
Argument syntax
| Arg | Type | Default | Allowed values | Meaning |
|---|---|---|---|---|
--focus <topic> |
parameterized | none | topic slug (kebab-case) | Topic focus — triggers focused mode if set. |
--market <code> |
parameterized | all per scope file | per fork's scope file (comma-separated) | Single or multi-market filter — triggers focused mode if set. |
--competitor <slug> |
parameterized | none | per fork's _scope.md competitor matrix |
Competitor filter — triggers focused mode if set. |
--horizon <Nd> |
parameterized | 7d (default mode), 30d (focused) | 7d / 30d / 90d / <N>d |
Lookback window for signals. |
--depth <level> |
parameterized | surface |
surface / deep |
Surface = ≤10 fetches, 1-page memo. Deep = ≤25 fetches, multi-section analysis. |
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.
- today First seen · 141 lines · 32 tokens per session scan A f781b19f5c02
market-radar is a skill published in the GitHub repository jaroslavsoucek-art/Giovanni (2 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 2,325 once invoked, about $0.0001 per session on Opus 5.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-10-17.
Other skills, from other repositories
continuum-tools-mcp
Connect MCP servers (Stdio/SSE/StreamableHTTP) to a Continuum agent, configure tool filtering, set up tool-context capture/injection (e.g. sessionid), and read run artifacts (UI widgets, structured tool data). Invoke when the user asks "connect MCP", "filesystem tool", "remote API tool", "auto-capture sessionid"…
continuum-handoffs
Build agent-to-agent transitions with Continuum's Handoff system — triage routing, history summarization modes (FULL/SUMMARY/RECENTN/HYBRID), cycle detection, depth tracking, return-to-parent. Invoke when the user asks "route customer requests to specialists", "agent that can transfer to another", "summarize history…
continuum-llm-providers
Pick the right LLM provider, configure structured outputs, control context-window compression, and use the LLMClient directly. Provider routing is by model-string prefix; LiteLLM has been removed. Also covers Smart Gateway integration for multi-provider routing. Invoke when the user asks about "switch to Claude"…
continuum-observability
Trace agent runs with Langfuse, decorate functions with @observe, collect latency/token/error metrics, and report errors. Invoke when the user asks about "see what the LLM was prompted with", "Langfuse traces", "track latency", "metrics dashboard", "error reporting", or "instrument my function".
continuum-temporal
Build durable agent workflows with Temporal — sequential/parallel/loop/conditional steps, human-in-the-loop approval gates, custom workflows and activities. Invoke when the user asks "long-running workflow", "approval gate", "human in the loop", "retry on failure", "workflow survives restart", or anything…
continuum-testing
Write tests for Continuum agents — mock LLM and memory clients via the DI Container, use fakeredis for sessions, snapshot agent responses, and run pytest-asyncio. Invoke when the user asks "test my agent", "mock the LLM", "fakeredis", "container injection", "pytest", or wants their CI to validate agent behavior…