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 agents/nomarj/sigil/risk-managergit clone --depth 1 https://github.com/NOMARJ/sigilWhat 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.00046 | $0.00521 |
| Opus 5 | $0.00023 | $0.00260 |
| Sonnet 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 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.
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.
- 2d ago First seen · 63 lines · 46 tokens per session scan A 1514a2add5d3
risk-manager is an agent published in the GitHub repository NOMARJ/sigil (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 46 tokens to every session and 521 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-31.
Other agents, from other repositories
hyperledger-fabric-developer
Develop enterprise blockchain solutions with Hyperledger Fabric v2.5 LTS and v3.x. Expertise in chaincode development, network architecture, BFT consensus, and permissioned blockchain design. Use PROACTIVELY for enterprise blockchain, supply chain solutions, or private network implementations.
data-scientist
Data analysis expert for SQL queries, BigQuery operations, and data insights. Use proactively for data analysis tasks and queries.
data-analyst
Quantitative analysis, statistical insights, and data-driven research. Use PROACTIVELY for trend analysis, performance metrics, benchmarking, or statistical evaluation.
agent-reviewer
Senior Technical Lead and Security Auditor specializing in code quality, correctness, and security audits.
e2e-testing
pnpm expo run:ios pnpm expo run:android.
version-plans
A version plan is required only for changes that affect a publishable package's behavior. Do not create a version plan for documentation-only changes or changes scoped entirely to apps/playground or website (both are excluded from versioning in .changeset/config.json).