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 OZmasterAI/Torus-Framework --skill reportgit clone --depth 1 https://github.com/OZmasterAI/Torus-FrameworkWrote 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/ozmasterai/torus-framework/report)<a href="https://agentmods.dev/skills/ozmasterai/torus-framework/report"><img src="https://agentmods.dev/badge/skills/ozmasterai/torus-framework/report/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/ozmasterai/torus-framework/report"><img src="https://agentmods.dev/badge/skills/ozmasterai/torus-framework/report.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.00000 | $0.00473 |
| Opus 5.5 | $0.00000 | $0.00189 |
| Sonnet 5.5 | $0.00000 | $0.00095 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
report 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.
What it actually says
/report — Session & Sprint Report Generator
When to use
When user says "report", "summary", "what did we do", "sprint report", "session summary", or wants a comprehensive overview of recent work.
Commands
/report— Current session report/report sprint— Full sprint report (all sessions on current branch)/report weekly— Weekly activity summary/report $ARGUMENTS— Custom report scope
Flow
1. GATHER
- Read LIVE_STATE.json for current session state
- Read LIVE_STATE.json for session history
- Check git log for recent commits on current branch
- Search memory for session-tagged entries:
search_knowledge("session") - Count current tests: run
python3 hooks/test_framework.py 2>&1 | grep RESULTS
2. METRICS
Collect and calculate:
- Code: files changed, lines added/removed (from git)
- Tests: total, passed, failed, new tests added
- Memory: total memories, new memories this session
- Skills: total skills, new skills created
- Agents: total agents, agents spawned this session
- Gates: fire counts, block counts from audit log
- Duration: session time from LIVE_STATE
3. NARRATIVE
Generate a human-readable summary:
- What was accomplished (bullet points)
- Key decisions made (from memory with type:decision)
- Issues encountered and resolved
- Research findings applied
4. COMPARISON
If previous report exists in memory:
- Calculate deltas for all metrics
- Highlight significant changes (>10% delta)
- Trend indicators: ↑ improving, ↓ regressing, → stable
5. OUTPUT
Format as markdown with sections:
## Session Report — #{session_number}
### Summary
### Metrics
### Key Decisions
### Issues & Fixes
### What's Next
Rules
- Always include raw numbers, not just percentages
- Save report to memory with type:benchmark,area:framework,report tags
- Never fabricate metrics — only report what can be verified
- Include "What's Next" section from LIVE_STATE.json
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 · 61 lines · 0 tokens per session scan A fde978208dc7
report is a skill published in the GitHub repository OZmasterAI/Torus-Framework (5 stars, last pushed 5mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 473 tokens. 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 skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.
rowboat-spaces
How to work as a member of Rowboat Spaces, the team chat where people and agents work together. Load it once per session, before acting on any request that reaches you from Rowboat; it covers your setup, mentions and hand-offs, the tools, and files.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…