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/ololand-ai/ololand-plugins/source-hierarchynpx skills add ololand-ai/ololand-plugins --skill source-hierarchygit clone --depth 1 https://github.com/ololand-ai/ololand-pluginsWrote 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/ololand-ai/ololand-plugins/source-hierarchy)<a href="https://agentmods.dev/skills/ololand-ai/ololand-plugins/source-hierarchy"><img src="https://agentmods.dev/badge/skills/ololand-ai/ololand-plugins/source-hierarchy.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.1 | $0.00037 | $0.00477 |
| Opus 5 | $0.00018 | $0.00238 |
| Sonnet 5 | $0.00007 | $0.00095 |
| Haiku 4.5 | $0.00004 | $0.00048 |
Grade A, and why
source-hierarchy 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
Source Hierarchy
Use the strongest available evidence for every material claim.
Priority order:
- CPA-audited financial statements — audited 10-K, 10-Q, audited stand-alone financials with an unqualified opinion. Highest authority.
- Tax returns and bank/source-system exports — Forms 1120 / 1065, signed bank statements, raw accounting system extracts (GL trial balance, AR/AP aging). Direct from the source system, not management's representation of it.
- Management models and CIMs — sell-side CIM, target management's operating model, board decks. High utility, but the management lens biases presentation. Treat as management view, not independent.
- Third-party market data — IBISWorld, S&P Capital IQ, PitchBook, sell-side research. Useful for context but not deal-specific.
- AI-extracted summaries — anything OloLand's risk/financial extraction pipeline produced from upstream documents. Always derivative — trace back to the underlying source for any material claim.
When sources conflict
Surface the conflict and prefer the higher-ranked source. Examples:
- 10-K reports $304.7M revenue (rank 1), management deck says $312M (rank 3) → cite both, lead with the 10-K, flag the $7.3M delta as a reconciliation item.
- Tax return shows a related-party transaction that the management model omitted → call out the omission; tax is higher rank than the model.
When the highest-available source is degraded
State the degradation explicitly. Examples:
- Auditor issued a going-concern qualification or material weakness disclosure → the audited statement is still rank 1, but lower confidence; surface the qualification before quoting any number from it.
- Tax return is from a different fiscal year than the 10-K → flag the temporal mismatch.
Output discipline
Never cite at a lower rank when a higher rank is available. If you cite an AI extraction (rank 5) when the same fact is in the 10-K (rank 1), the answer fails the verifier-stack standard.
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 · 33 lines · 37 tokens per session scan A cce826c8a8ad
source-hierarchy is a skill published in the GitHub repository ololand-ai/ololand-plugins (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 37 tokens to every session and 477 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-09-03.
Other skills, from other repositories
sector-rotation
行业轮动分析——申万行业景气度评分、行业动量排名、产业链传导、估值/盈利/资金流多维比较框架.
strategy-pivot-designer
Detect backtest iteration stagnation and generate structurally different strategy pivot proposals when parameter tuning reaches a local optimum.
twitter-reader
Read Twitter/X for financial research using opencli (read-only). Use this skill whenever the user wants to read their Twitter feed, search for financial tweets, view bookmarks, look up user profiles, or gather market sentiment from Twitter/X. Triggers include: "check my feed", "search Twitter for", "show my…
chenhao-limit-up
Use when evaluating A-share limit-up (涨停板) setups through Chen Hao's sentiment and momentum lens: market emotion cycles, board strength, follow-through, and short-term aggressive momentum trading.
trading-risk-gate
Unified pre-trade safety gate: Ruin check (Law #1), ergodicity audit, and win-rate dominance validation. Absorbs: ergodicity-check, law-of-ruin, win-rate-dominance.
vectorbt
High-performance vectorized backtesting with parameter optimization, portfolio simulation, and rich performance metrics.