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 GuilhemBusset/agentic-or-workshop --skill data-signal-analysis-teamgit clone --depth 1 https://github.com/GuilhemBusset/agentic-or-workshopWrote 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/guilhembusset/agentic-or-workshop/data-signal-analysis-team)<a href="https://agentmods.dev/skills/guilhembusset/agentic-or-workshop/data-signal-analysis-team"><img src="https://agentmods.dev/badge/skills/guilhembusset/agentic-or-workshop/data-signal-analysis-team/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/guilhembusset/agentic-or-workshop/data-signal-analysis-team"><img src="https://agentmods.dev/badge/skills/guilhembusset/agentic-or-workshop/data-signal-analysis-team.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.00038 | $0.00782 |
| Opus 5 | $0.00019 | $0.00391 |
| Sonnet 5 | $0.00008 | $0.00156 |
| Haiku 4.5 | $0.00004 | $0.00078 |
Grade A, and why
data-signal-analysis-team 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Signal Analysis Team Skill
Use this skill when the request is to analyze the workshop dataset, not to build or run an optimization model.
Goal
Produce one autonomous analysis of workshop/data that surfaces:
- data structure and coverage,
- key integrity/consistency checks,
- demand/capacity/cost/risk signals relevant to the disaster-relief planning problem,
- the most important data-driven takeaways.
Do not run a team loop. Do not emit JSON artifacts. Do not generate multiple reports.
Required Tooling
Use MCP server data-explorer-csv:
describe_csv_schema(file_path)for schema/profile discovery,query_csv(file_path, query)for read-only SQL checks.
Rules:
- Analyze only files under
workshop/data. - One tool call targets one CSV file.
- SQL must be read-only and reference
csv_data.
Three-Agent Internal Workflow
Agent 1: Scope Agent (what)
- Define the exact analysis objective from the exercise statement.
- Select priority files and checks to answer:
- Is data complete and coherent for the planning context?
- What are the strongest operational signals (demand, capacity, arc costs, scenario risk)?
- Create a short checklist of required findings before any conclusion.
Agent 2: Method Agent (how)
- Execute schema discovery on relevant CSVs using
describe_csv_schema. - Run focused
query_csvchecks to extract evidence. - At minimum, cover:
towns.csv: demand base, critical towns, service targets.depots.csv: capacities, fixed/opening-related signals.arcs.csv: lane availability and shipping cost distribution.scenarios.csvandscenario_demands.csv: uncertainty scale and probability sanity.designs.csv,scenario_flows.csv,scenario_scores.csv: design behavior and risk/cost outcomes.
- Keep results concise and evidence-backed.
Agent 3: Verification Agent (works correctly)
- Verify that all required checks were actually executed.
- Verify no claim is unsupported by a tool result.
- Verify the final report is a single markdown file and contains only high-value findings.
- Remove weak or redundant observations.
What ships with it
1 file 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.
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 · 84 lines · 38 tokens per session scan A fdb01c5bbd47
data-signal-analysis-team is a skill published in the GitHub repository GuilhemBusset/agentic-or-workshop (2 stars, last pushed 6mo ago), licensed MIT. It adds 38 tokens to every session and 782 once invoked, about $0.0002 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
agent-platform-rag-engine-management
Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
google-cloud-solution-agentic-analytics-spark-knowledge-catalog
Discovers requirements and generates guidance to design and deploy a governed, secure agentic-analytics solution for data that's distributed across Google Cloud, other cloud providers, or on-premises. Data that's outside Google Cloud (such as data from Databricks, Snowflake, Salesforce, SAP, or Oracle systems) is…
training-check
Interactively monitor training metrics from the current Codex session, periodically checking WandB or fallback logs for NaN, divergence, plateaus, and broken runs.
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.