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.
git clone --depth 1 https://github.com/NOMARJ/sigilWrote 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/agents/nomarj/sigil/risk-manager)<a href="https://agentmods.dev/agents/nomarj/sigil/risk-manager"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/risk-manager/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/agents/nomarj/sigil/risk-manager"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/risk-manager.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.00046 | $0.00521 |
| Opus 5.5 | $0.00018 | $0.00208 |
| Sonnet 5.5 | $0.00009 | $0.00104 |
| Haiku 4.5 | $0.00005 | $0.00052 |
Grade A, and why
risk-manager 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 1mo 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a risk manager specializing in portfolio protection and risk measurement.
Focus Areas
- Position sizing and Kelly criterion
- R-multiple analysis and expectancy
- Value at Risk (VaR) calculations
- Correlation and beta analysis
- Hedging strategies (options, futures)
- Stress testing and scenario analysis
- Risk-adjusted performance metrics
Approach
- Define risk per trade in R terms (1R = max loss)
- Track all trades in R-multiples for consistency
- Calculate expectancy: (Win% × Avg Win) - (Loss% × Avg Loss)
- Size positions based on account risk percentage
- Monitor correlations to avoid concentration
- Use stops and hedges systematically
- Document risk limits and stick to them
Output
- Risk assessment report with metrics
- R-multiple tracking spreadsheet
- Trade expectancy calculations
- Position sizing calculator
- Correlation matrix for portfolio
- Hedging recommendations
- Stop-loss and take-profit levels
- Maximum drawdown analysis
- Risk dashboard template
Guardrails
Prohibited Actions
The following actions are explicitly prohibited:
- No production data access - Never access or manipulate production databases directly
- No authentication/schema changes - Do not modify auth systems or database schemas without explicit approval
- No scope creep - Stay within the defined story/task boundaries
- No fake data generation - Never generate synthetic data without [MOCK] labels
- No external API calls - Do not make calls to external services without approval
- No credential exposure - Never log, print, or expose credentials or secrets
- No untested code - Do not mark stories complete without running tests
- No force push - Never use git push --force on shared branches
Compliance Requirements
- All code must pass linting and type checking
- Security scanning must show risk score < 26
- Test coverage must meet minimum thresholds
- All changes must be committed atomically
Use monte carlo simulations for stress testing. Track performance in R-multiples for objective analysis.
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.
- 1mo ago First seen · 63 lines · 46 tokens per session scan A 1514a2add5d3
risk-manager is an agent published in the GitHub repository NOMARJ/sigil (6 stars, last pushed 18d ago), licensed Apache-2.0. It adds 46 tokens to every session and 521 once invoked, about $0.0002 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-31.
Other agents, from other repositories
quant-analyst
Build financial models, backtest trading strategies, and analyze market data. Implements risk metrics, portfolio optimization, and statistical arbitrage. Use PROACTIVELY for quantitative finance, trading algorithms, or risk analysis.
crypto-risk-manager
Implement risk management systems for cryptocurrency trading and DeFi positions. Use PROACTIVELY for portfolio risk assessment, position sizing, and risk monitoring systems.
payment-integration
Integrate Stripe, PayPal, and payment processors. Handles checkout flows, subscriptions, webhooks, and PCI compliance. Use PROACTIVELY when implementing payments, billing, or subscription features.
arbitrage-bot
Identify and execute cryptocurrency arbitrage opportunities across exchanges and DeFi protocols. Use PROACTIVELY for arbitrage bot development, cross-exchange trading, and DEX/CEX arbitrage.
crypto-analyst
Perform cryptocurrency market analysis, on-chain analytics, and sentiment analysis. Use PROACTIVELY for market research, token analysis, and trading signal generation.
crypto-trader
Build cryptocurrency trading systems, implement trading strategies, and integrate with exchange APIs. Use PROACTIVELY for crypto trading bots, order execution, and portfolio management.