What is analyze-company-data?

A skill for answering questions about company metrics, trends, records, and other analysis in Basedash. Basedash analyzes data connected to a company workspace.

Use it for metric lookups, trend analysis, comparisons, and saving a returned result as a chart.

It keeps the analysis tied to the user's accessible data and preserves context when a question continues an earlier conversation.

analyze-company-data — Skill by Basedash

Install

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.

agentmods

npx agentmods add skills/basedash/agent-plugin/analyze-company-data

Any agent

npx skills add Basedash/agent-plugin --skill analyze-company-data

Clone the repo

git clone --depth 1 https://github.com/Basedash/agent-plugin

Made for: Claude Code, Codex.

Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 175 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00027	$0.00175
Opus 5	$0.00014	$0.00088
Sonnet 5	$0.00005	$0.00035
Haiku 4.5	$0.00003	$0.00017

Measured yesterday against content hash fbb2e63fda6f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

analyze-company-data 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 yesterday.

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.

skills/analyze-company-data/SKILL.md · 14 lines

What it actually says

Analyze company data

Call ask_question with the user's question.
When continuing an existing Basedash conversation, pass its chat_id so the analysis keeps the prior context.
If the user first needs to know what data is available, call get_data_sources.
Treat tool results as limited to sources the authenticated user can access in their Basedash workspace.
Report the returned result faithfully. Do not invent SQL, numbers, sources, or conclusions that the tool did not return.
If the user asks to save the result as a chart, call create_chart with clear natural-language instructions and include dashboard_id when they selected a dashboard.

Changes

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.

yesterday First seen · 14 lines · 27 tokens per session scan A fbb2e63fda6f

Subscribe to this mod's changes

analyze-company-data is a skill published in the GitHub repository Basedash/agent-plugin (0 stars, last pushed 4d ago), licensed MIT. It adds 27 tokens to every session and 175 once invoked, about $0.0001 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.

Analytics and metrics

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens