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 agentmods add skills/demondamon/agenticx/agenticx-query-data-sourcenpx skills add DemonDamon/AgenticX --skill agenticx-query-data-sourcegit clone --depth 1 https://github.com/DemonDamon/AgenticXWrote 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/demondamon/agenticx/agenticx-query-data-source)<a href="https://agentmods.dev/skills/demondamon/agenticx/agenticx-query-data-source"><img src="https://agentmods.dev/badge/skills/demondamon/agenticx/agenticx-query-data-source.svg" alt="Measured on agentmods" 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 | $0.00049 | $0.01705 |
| Opus 5 | $0.00024 | $0.00852 |
| Sonnet 5 | $0.00010 | $0.00341 |
| Haiku 4.5 | $0.00005 | $0.00170 |
Grade A, and why
agenticx-query-data-source 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 4d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Query Data Source
When to use
- Any question about stock price, financial indicators, macro economic data, company registry, academic citation counts, or legal statute text that has a real, checkable current value.
- Do NOT answer from training memory for these categories — training data is stale and the user can verify against a real source.
- Call
list_data_sourcesfirst when unsure which plugin or API fits (optionaldomain:finance/macro/academic/enterprise/legal).
How to call
list_data_sources(domain="finance")— discover enabled plugins andapi_namevalues.query_data_source(data_source_name=..., api_name=..., params={...})— fetch structured JSON.- Default chart window:
days: 60(≈3 个月交易日). A candlestick chart with only 5–10 bars looks sparse/empty in the chat widget, so this is the default for any "走势/行情/表现如何" style question — including casual phrasing like "最近一周走势" (interpret as "show me how it's been doing lately", not literally 5 trading days). - Only request a shorter window when the user gives an unambiguous analytical ask for an
exact short range (e.g. "对比昨天和前天的收盘价" or "最近3个交易日的具体数字"). Map common asks:
1个月→days:20,3个月→days:60(默认),6个月→days:120,1年→days:250.
- Default chart window:
- For time-series results (price history, macro trend), must follow with
show_widget:- Prefer structured JSON (Desktop renders via ECharts):
- The top-level
"type": "stock_chart"field is MANDATORY. Omitting it makes the Desktop client treat the payload as a generic HTML widget and render the raw JSON text instead of a chart — always double-check this field is present before callingshow_widget.
Single stock:
{
"type": "stock_chart",
"title": "火炬电子 603678",
"chart_type": "candlestick",
"data_source_label": "获取数据 | AkShare(免费行情)",
"points": [
{"date": "2026-07-01", "open": 80, "high": 90, "low": 78, "close": 85, "volume": 120000}
],
"attribution": "数据来源:AkShare"
}
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.
- 4d ago First seen · 124 lines · 49 tokens per session scan A 6eb47b7d40a8
agenticx-query-data-source is a skill published in the GitHub repository DemonDamon/AgenticX (219 stars, last pushed 4d ago), licensed Apache-2.0. It adds 49 tokens to every session and 1,705 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-30.
Other skills, from other repositories
skill-creator
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
tmux
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
weather
Get current weather and forecasts (no API key required).
github
Interact with GitHub using the gh CLI. Use gh issue, gh pr, gh run, and gh api for issues, PRs, CI runs, and advanced queries.
memory
Search conversation history and understand Dream-managed profile and memory files.
browser-use
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, or extract information from web pages.