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/monarchjuno/tradingcodex/tcx-plannpx skills add monarchjuno/tradingcodex --skill tcx-plangit clone --depth 1 https://github.com/monarchjuno/tradingcodexWrote 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/monarchjuno/tradingcodex/tcx-plan)<a href="https://agentmods.dev/skills/monarchjuno/tradingcodex/tcx-plan"><img src="https://agentmods.dev/badge/skills/monarchjuno/tradingcodex/tcx-plan.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.00085 | $0.00891 |
| Opus 5 | $0.00043 | $0.00445 |
| Sonnet 5 | $0.00017 | $0.00178 |
| Haiku 4.5 | $0.00009 | $0.00089 |
Grade A, and why
tcx-plan 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Workflow
Use this skill to turn a vague or execution-sensitive request into a compact
user mandate. The mandate feeds $tcx-workflow for immediate runs and
$tcx-automate for recurring runs. It is conversation context, not a
server-generated plan, semantic lane, selected team, role ceiling, or DAG. Head
Manager still interprets the live request, begins the lightweight analysis run,
and dynamically chooses or revises exact fixed roles from accepted evidence.
Procedure
- Restate the user's objective, subject scope, time or as-of horizon, requested output, and whether the work is immediate or recurring.
- Extract binding constraints: symbols or universe when supplied, Strategy or account scope when explicitly selected, allowed actions, blocked actions, approval posture, evidence requirements, stop conditions, and schedule when recurring.
- Ask only for missing fields whose answer would materially change the result,
suitability, action authority, automation arming, or stop condition. Leave
analytical decomposition and role choice to
$tcx-workflow. - Preserve explicit prohibitions in the user's own terms. Do not translate them into a keyword classification, fixed role list, or default team.
- Write reader-facing questions, summaries, and the
Workflow Mandatein the user's language from the original request unless the user explicitly asks for another language. - Produce a compact
User Mandatewith the fields below, then hand off:- immediate investment work:
READY_FOR_DYNAMIC_ANALYSIS - recurring workflow:
READY_FOR_AUTOMATION_PREFLIGHT - missing material fields:
NEEDS_CLARIFICATION - server/build request:
SERVER_OR_BUILD_HANDOFF - unsafe or unsupported request:
BLOCKED_BY_SCOPE
- immediate investment work:
Question Discipline
- Ask at most three focused questions at a time.
- Do not assign a default analytical category, stage sequence, or analyst team to a broad request. Ask only when unresolved scope would materially change the requested outcome; otherwise let Head Manager begin with the smallest useful question.
- Do not block general research on broker, account, or profile details that are irrelevant to the requested output.
- Require explicit answers for order drafting, paper execution, live execution, account/broker scope, pre-approved mandates, and recurring schedules.
- If automation is requested, require schedule, blocker policy, and expiry or rearm condition before
READY_FOR_AUTOMATION_PREFLIGHT.
What ships with it
1 file 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.
- 4d ago First seen · 87 lines · 85 tokens per session scan A 7b7e1d2e2314
tcx-plan is a skill published in the GitHub repository monarchjuno/tradingcodex (366 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 85 tokens to every session and 891 once invoked, about $0.0004 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
consulting-analysis
Use this skill when the user requests to generate, create, or write professional research reports including but not limited to market analysis, consumer insights, brand analysis, financial analysis, industry research, competitive intelligence, investment due diligence, or any consulting-grade analytical report. This…
agent-agentic-payments
Agent skill for agentic-payments - invoke with $agent-agentic-payments.
agent-payments
Agent skill for payments - invoke with $agent-payments.
company-research
A 股个股研究六阶段 SOP(profile → financials → estimates → valuation → risk → report),Phase 0 范围 = 财务估值闭环。当任务是研究 / 分析 / 评估一只或多只已指定代码的 A 股个股时使用;规定每阶段取哪些数据、调哪些 calc 函数、必须落盘什么产物、过什么 Gate。不用于:从市场中筛选标的、泛行业讨论、概念解释、给投资动作建议。.
moai-foundation-core
Provides MoAI-ADK foundational principles including TRUST 5 quality framework, SPEC-First DDD methodology, delegation patterns, progressive disclosure, agent catalog reference, and token budget management (absorbed from moai-foundation-context). Use when referencing TRUST 5 gates, SPEC workflow, or context window…
moai-domain-html-report
Markdown-to-single-file-HTML report renderer. Six modes (status, incident, plan, explainer, financial, pr) selected by report type, crossed with three audience tiers (expert, basic, learn) derived from the active output style. The basic and learn tiers enrich the HTML with mermaid flowcharts, worked examples, and…