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 FTShare-Lab/FTShare-skill --skill ashare-code-change-timelinegit clone --depth 1 https://github.com/FTShare-Lab/FTShare-skillWrote 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/ftshare-lab/ftshare-skill/ashare-code-change-timeline)<a href="https://agentmods.dev/skills/ftshare-lab/ftshare-skill/ashare-code-change-timeline"><img src="https://agentmods.dev/badge/skills/ftshare-lab/ftshare-skill/ashare-code-change-timeline/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/ftshare-lab/ftshare-skill/ashare-code-change-timeline"><img src="https://agentmods.dev/badge/skills/ftshare-lab/ftshare-skill/ashare-code-change-timeline.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.00059 | $0.00574 |
| Opus 5.5 | $0.00024 | $0.00230 |
| Sonnet 5.5 | $0.00012 | $0.00115 |
| Haiku 4.5 | $0.00006 | $0.00057 |
Grade A, and why
ashare-code-change-timeline 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 2d 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.
What it actually says
A 股代码变更时间线
接口：GET /api/v1/market/data/stk_code_change_timeline。无入参，全量返回全部代码变更事件，不分页。
python <RUN_PY> ashare-code-change-timeline
成功响应为 code/message/data，data 为记录数组，每条记录描述一次换码事件：
| 字段 | 类型 | 说明 |
|---|---|---|
| stock_name | string | 证券名称 |
| new_code | string | 换码后的新代码 |
| new_code_start | string | 新代码启用起始日期 YYYYMMDD |
| old_code | string | 换码前的旧代码 |
| old_code_start | string | 旧代码启用起始日期 YYYYMMDD |
| old_code_end | string | 旧代码停用日期 YYYYMMDD |
| old_last_trade_dt | string | 旧代码最后交易日 YYYYMMDD |
| new_first_trade_dt | string | 新代码首个交易日 YYYYMMDD |
| market | string | 所属市场，取值 SH / SZ / BJ |
{
"code": 200,
"message": "success",
"data": [
{
"stock_name": "上海医药",
"new_code": "601607",
"new_code_start": "20100305",
"old_code": "600849",
"old_code_start": "19940324",
"old_code_end": "20100304",
"old_last_trade_dt": "20100225",
"new_first_trade_dt": "20100309",
"market": "SH"
}
]
}
注意事项
- 无入参，一次性返回全部记录（覆盖 1993 年以来的 A 股代码变更）。
- 日期字段均为
YYYYMMDD字符串（如20181226），非时间戳；代码为六位纯数字，不带交易所后缀。 market取值SH（上交所）/SZ（深交所）/BJ（北交所）。- 若需要按单只股票查询其代码变更历史，请使用
ashare-code-change子 skill。
What ships with it
2 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.
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.
- 2d ago First seen · 54 lines · 59 tokens per session scan A 08b12487f754
ashare-code-change-timeline is a skill published in the GitHub repository FTShare-Lab/FTShare-skill (65 stars, last pushed 2d ago), licensed MIT. It adds 59 tokens to every session and 574 once invoked, about $0.0002 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-15.
Other skills, from other repositories
tickdb-market-data
A real-time market-data API for foreign exchange, metals, indexes, stocks, and cryptocurrencies. An API is a service that software can call to request data.
defeatbeta-earnings-analysis
Create professional equity research earnings update reports (8-12 pages, 3,000-5,000 words) analyzing quarterly results for companies already under coverage. Fast-turnaround format focusing on beat/miss analysis, key metrics, updated estimates, and revised thesis. Includes 1-3 summary tables and 8-12 charts. Use when…
defeatbeta-earnings-preview
Build pre-earnings analysis with normalized baselines, weighted decision models, company-specific veto gates, scenario frameworks, catalysts, historical reactions, and options-implied moves. Use before a company reports quarterly earnings to prepare positioning notes or bilingual three-page PDF reports.
defeatbeta-analyst
Professional financial analysis using 60+ market data APIs. Use for: company fundamentals (revenue, margins, EPS, balance sheet), valuation (P/E, P/B, P/S, PEG, DCF, intrinsic value), profitability (ROE, ROA, ROIC), growth trends (YoY revenue/earnings/FCF), earnings transcripts (key data, changes, guidance), industry…
defeatbeta-earnings-key-data
Run one of three traceable earnings-call transcript templates through the DefeatBeta MCP tools: (1) extract current-quarter results plus next-quarter and full-year guidance, (2) extract factual QoQ or YoY financial-metric change sentences, or (3) extract numerical forward-looking forecast sentences with…
sprr
Single PR reviewer for awesome-quant. Use when the user asks to review, validate, comment on, label, close, or merge one specific pull request that adds README.md entries. Triggers include "sprr", "review PR", "check PR", and "validate contribution".