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 desirecore/market --skill tianyancha-riskgit clone --depth 1 https://github.com/desirecore/marketWrote 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/desirecore/market/tianyancha-risk)<a href="https://agentmods.dev/skills/desirecore/market/tianyancha-risk"><img src="https://agentmods.dev/badge/skills/desirecore/market/tianyancha-risk/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/desirecore/market/tianyancha-risk"><img src="https://agentmods.dev/badge/skills/desirecore/market/tianyancha-risk.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.00097 | $0.01884 |
| Opus 5 | $0.00048 | $0.00942 |
| Sonnet 5 | $0.00019 | $0.00377 |
| Haiku 4.5 | $0.00010 | $0.00188 |
Grade A, and why
tianyancha-risk scanned grade A with 1 finding 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Invocation**: HTTP GET (curl / HttpRequest tool) How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tianyancha Risk Query
L0: One-Sentence Summary
Input a company name, call the Tianyancha risk-info API, and return a structured risk profile (self / related-party / historical / warning, four categories).
L1: Overview
- Data source: Tianyancha Open Platform
risk/riskInfo/2.0 - Auth: Token (
Authorizationheader, without theBearerprefix) - Invocation: HTTP GET (curl / HttpRequest tool)
- Prerequisites: a valid Token with the risk API enabled
Credential Setup
This skill requires a Tianyancha Open Platform Token:
- Register an enterprise account at the Tianyancha Open Platform
- Purchase/enable an API package (
risk/riskInfo/2.0is authorized per package tier) - Export the token as the environment variable
TIANYANCHA_TOKEN, or replace the{TIANYANCHA_TOKEN}placeholder below
L2: Procedure
1. Build the request
curl -s --max-time 30 --ssl-no-revoke \
"https://open.api.tianyancha.com/services/open/risk/riskInfo/2.0?keyword={company-name-URL-encoded}" \
-H "Authorization: ${TIANYANCHA_TOKEN}"
Parameters:
| Param | Value | Notes |
|---|---|---|
| keyword | Company name (URL-encoded) | e.g. 华为技术有限公司 |
| Authorization | {TIANYANCHA_TOKEN} |
Token in header, no Bearer prefix (adding one returns 300009) |
2. Interpret the response
error_code == 0andreason == "ok": success, extractresult.riskList[]error_code == 300009: account error — wrong token or aBearerprefix was addederror_code == 300005: no permission for this API — the token does not cover iterror_code == 300008: missing parameter — check keyword
3. Response structure
result contains:
riskLevel: overall risk levelriskList[]: four risk categories (each with name / count / type / list[])
| Category | type | Meaning |
|---|---|---|
| Self risk | 1 | The company's own judicial/business risks (court hearings / rulings / case filings / court announcements / judicial auctions) |
| Related-party risk | 2 | Risks of shareholders, executives, invested companies |
| Historical risk | 3 | Closed historical risks (historical filings / hearings / dishonest-debtor history) |
| Early warnings | 0 | Business-registration changes (investor / key-personnel / registered-capital / legal-representative changes, bankruptcy cases) |
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.
- 6d ago First seen · 155 lines · 97 tokens per session scan A 5706e32343de
tianyancha-risk is a skill published in the GitHub repository desirecore/market (2 stars, last pushed today), licensed MIT. It adds 97 tokens to every session and 1,884 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.
Other skills, from other repositories
insurance-expert
Expert-level insurance systems, underwriting, claims processing, actuarial analysis, risk assessment, and insurtech solutions. Use when the user mentions underwriting, claims, actuarial, risk, or insurtech, or when the task involves Insurance Systems, Insurance Types, Standards and Regulations, or Claims Processing.
stablecoin-risk-check
Assess stablecoin safety and risk profile across 500+ protocols. Covers depeg history, reserve composition, audit status, regulatory exposure, and market cap trends for major stablecoins (USDT, USDC, DAI, USDS, USDe, FDUSD, PYUSD, GHO, crvUSD, and more). Use when users ask "is this stablecoin safe?", "stablecoin…
corporate-registry-investigation
Use when users say "Companies House search", "investigate this UK company", "check officers/PSCs/charges", "registry snapshot", "group structure", "filing history", or need UK company profile, filings, risk leads, and registry evidence reviewed without unsupported allegations.
Diligence Issue Extraction
Use when reviewing provided due-diligence documents for an M&A or investment transaction to extract material issues into a structured, severity-sorted issues memo for attorney review.
stablecoin-risk-check
Assess stablecoin safety and risk profile. Covers depeg history, reserve composition, audit status, regulatory exposure, and market cap trends for major stablecoins (USDT, USDC, DAI, USDS, USDe, FDUSD, PYUSD, GHO, crvUSD, and more). Use when users ask "is this stablecoin safe?", "stablecoin risk", "depeg risk", or…
qcc-risk-screen
A full risk-screening workflow for Chinese companies using Qichacha, a business-information service. It checks legal, enforcement, tax, bankruptcy, ownership, operating, and other company-risk records.