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 tradermonty/hermes-trading-research-agent-work-package --skill trading-cron-brief-writergit clone --depth 1 https://github.com/tradermonty/hermes-trading-research-agent-work-packageWrote 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/tradermonty/hermes-trading-research-agent-work-package/trading-cron-brief-writer)<a href="https://agentmods.dev/skills/tradermonty/hermes-trading-research-agent-work-package/trading-cron-brief-writer"><img src="https://agentmods.dev/badge/skills/tradermonty/hermes-trading-research-agent-work-package/trading-cron-brief-writer/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/tradermonty/hermes-trading-research-agent-work-package/trading-cron-brief-writer"><img src="https://agentmods.dev/badge/skills/tradermonty/hermes-trading-research-agent-work-package/trading-cron-brief-writer.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.00031 | $0.00343 |
| Opus 5.5 | $0.00012 | $0.00137 |
| Sonnet 5.5 | $0.00006 | $0.00069 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
trading-cron-brief-writer 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 2mo 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
Trading Cron Brief Writer
Use this skill whenever a scheduled trading routine is running.
Formatting rules
- Start with a one-line status:
Risk posture: ... - Use compact Markdown.
- Avoid long essays in messaging channels.
- Include a
Data freshnesssection. - Include a
Human next actionssection. - If no significant change exists and the job prompt permits silence, output exactly
[SILENT]as the first token.
Brief template
# <Routine name> — <date>
**Risk posture:** <risk-on / neutral / risk-off / blocked>
**Primary reason:** <one sentence>
## 1. Key changes
- ...
## 2. Market regime
- Breadth:
- Uptrend participation:
- Distribution/top risk:
## 3. Events / earnings
- ...
## 4. Watchlist / review queue
| Ticker | Setup | Thesis | Invalidation | Follow-up |
|---|---|---|---|---|
## 5. Human next actions
- ...
## Data freshness
- ...
Degraded mode
If market data, API keys, or external skills are unavailable:
- Say which component is missing.
- Provide what can be done offline.
- Provide setup steps.
- Do not fabricate numbers.
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.
- 2mo ago First seen · 62 lines · 31 tokens per session scan A 55d908c4e080
trading-cron-brief-writer is a skill published in the GitHub repository tradermonty/hermes-trading-research-agent-work-package (48 stars, last pushed 5mo ago), licensed MIT. It adds 31 tokens to every session and 343 once invoked, about $0.0001 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-08-30.
trading-cron-brief-writer compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| trading-cron-brief-writertradermonty/hermes-trading-research-agent-work-package | Skill | 48 | 5mo ago | MIT | A | 31 | Claude Code, Codex |
| sector-rotationHKUDS/Vibe-Trading | Skill | 38k | yesterday | MIT | A | 39 | Claude Code, Codex |
| twitter-readerhimself65/finance-skills | Skill | 3.5k | 2d ago | MIT | A | 110 | Claude Code |
| strategy-pivot-designertradermonty/claude-trading-skills | Skill | 3.7k | 2d ago | MIT | A | 28 | Claude Code, Codex |
| energy-procurementhashgraph-online/awesome-codex-plugins | Skill | 1.5k | yesterday | Apache-2.0 | A | 93 | Claude Code, Codex |
| airdrop-hunting-guidenirholas/three.ws | Skill | 269 | yesterday | Apache-2.0 | A | 54 | Claude Code, Codex |
| multi-expert-analyzerdigoal/blog | Skill | 8.6k | 2d ago | GPL-2.0 | A | 292 | Codex |