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 xingwudao/open-xquant --skill build-rulegit clone --depth 1 https://github.com/xingwudao/open-xquantWrote 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/xingwudao/open-xquant/build-rule)<a href="https://agentmods.dev/skills/xingwudao/open-xquant/build-rule"><img src="https://agentmods.dev/badge/skills/xingwudao/open-xquant/build-rule/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/xingwudao/open-xquant/build-rule"><img src="https://agentmods.dev/badge/skills/xingwudao/open-xquant/build-rule.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Memory Poisoning · line 159 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
- medium Agent Snooping · line 165 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 166 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00046 | $0.01050 |
| Opus 5 | $0.00023 | $0.00525 |
| Sonnet 5 | $0.00009 | $0.00210 |
| Haiku 4.5 | $0.00005 | $0.00105 |
Grade A, and why
build-rule 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 10d 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rule Builder
You help the user add risk and exit logic without overstating current spec support.
Current Execution Model
Rules are Python objects passed to Engine.run(..., rules=[...]) or added by
the spec compiler internally. The audited CLI spec path does not support a
generic top-level rules: YAML section or oxq backtest run --rules, but it
does support a narrow whitelist under portfolio.rules.
In current Engine.step():
- pre-trade rule effects consumed:
RuleResult.weights,RuleResult.hold - post-trade rule effects consumed:
RuleResult.target_positions - declared but not currently consumed by
Engine:RuleResult.constraints
Do not tell the user that a constraints field will affect execution unless
you have verified the engine path being used consumes it.
Built-in Rules
Inspect the live registry:
uv run python - <<'PY'
import oxq
print(sorted(oxq.list_rules()))
PY
Common built-ins:
ExitRuleStopLossRuleTakeProfitRuleTrailingStopRuleMaxDrawdownRiskDailyLossLimitRiskMaxHoldingsRuleRebalanceFrequencyRuleCalendarRebalanceRuleBlacklistRule
Safe CLI Path
For Crossover specs, compile_run() automatically adds ExitRule using the
declared fast and slow columns. For every explicit portfolio.rules item,
all required params must be present; do not rely on runtime constructor
defaults.
For rebalance throttling by trading-session count, use:
execution:
rebalance:
frequency: daily
interval_days: 5
or:
portfolio:
rules:
rebalance:
type: RebalanceFrequencyRule
params:
interval_days: 5
For calendar rebalance, use the execution schedule. The compiler emits
CalendarRebalanceRule internally:
execution:
rebalance:
frequency: monthly
schedule: month_start
Supported audited portfolio.rules entries are:
portfolio:
rules:
stop_loss:
type: StopLossRule
params:
threshold: 0.05
take_profit:
type: TakeProfitRule
params:
threshold: 0.20
trailing_stop:
type: TrailingStopRule
params:
trail_pct: 0.08
max_drawdown:
type: MaxDrawdownRisk
params:
max_drawdown: 0.15
daily_loss:
type: DailyLossLimitRisk
params:
max_daily_loss: 0.03
max_holdings:
type: MaxHoldingsRule
params:
max_holdings: 10
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.
- 10d ago First seen · 182 lines · 46 tokens per session scan A 62623aebc648
build-rule is a skill published in the GitHub repository xingwudao/open-xquant (127 stars, last pushed 8d ago), licensed MIT. It adds 46 tokens to every session and 1,050 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
sector-rotation
An analysis framework for comparing industries in the Chinese A-share stock market, using business conditions, price momentum, valuation, and money flows. It produces rankings and higher- or lower-allocation suggestions.
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
A framework for judging Chinese A-share stocks that have reached the daily price-rise limit, using market mood, sector leadership, and trading momentum.
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.
furusato
A Japanese hometown-tax donation manager for furusato nozei, a system where donations to municipalities can qualify for an income-tax or local-tax deduction. It reads donation receipts, stores donation records, and calculates deduction limits.