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 commands/xsovad06/sova/quarterly-reportgit clone --depth 1 https://github.com/xsovad06/sovaWrote 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/commands/xsovad06/sova/quarterly-report)<a href="https://agentmods.dev/commands/xsovad06/sova/quarterly-report"><img src="https://agentmods.dev/badge/commands/xsovad06/sova/quarterly-report.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.00016 | $0.00843 |
| Opus 5 | $0.00008 | $0.00421 |
| Sonnet 5 | $0.00003 | $0.00169 |
| Haiku 4.5 | $0.00002 | $0.00084 |
Grade A, and why
quarterly-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 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quarterly Impact Report Generator
Generate a comprehensive quarterly impact report pulling data from git history and GitHub (PRs, Issues). Useful for goal progress updates, manager 1:1s, and promotion readiness.
Parameters
The user may optionally specify:
- A quarter (e.g., "Q1 2026", "Q2 2026"). Default: current quarter based on today's date.
- A specific repo. Default: current repository.
Determine quarter date ranges:
- Q1: January 1 - March 31
- Q2: April 1 - June 30
- Q3: July 1 - September 30
- Q4: October 1 - December 31
Data Collection
Run ALL of the following data collection commands in parallel:
1. Git Commits
git log --author="$(git config user.name)" --since="QUARTER_START" --until="QUARTER_END" --format="%H|%ad|%s" --date=short
Count total commits, unique days with commits.
2. Git Line Stats
git log --author="$(git config user.name)" --since="QUARTER_START" --until="QUARTER_END" --shortstat --format=""
Sum insertions and deletions.
3. GitHub PRs Authored (Merged)
gh pr list --author @me --state merged --limit 100 --json number,title,mergedAt,additions,deletions,changedFiles,createdAt
Filter to the quarter by mergedAt date. Calculate total PRs, additions/deletions, avg cycle time.
4. GitHub PRs Reviewed
gh search prs --reviewed-by @me --repo <OWNER/REPO> --limit 100 --json number,title,updatedAt,state
Filter to the quarter. Count total reviews given.
5. GitHub Issues Completed
gh issue list --assignee @me --state closed --limit 100 --json number,title,labels,closedAt
Filter to the quarter by closedAt date. Count by label/type. List each with number, title, and labels.
6. Open/In-Progress Work
gh issue list --assignee @me --state open --json number,title,labels,milestone
Report Structure
Quarterly Impact Report: [Quarter] [Year]
Author: [User Name] | Team: [Team Name] Period: [Start Date] - [End Date] Generated: [Today's Date]
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 · 118 lines · 16 tokens per session scan A c9d404e57446
quarterly-report is a command published in the GitHub repository xsovad06/sova (2 stars, last pushed today), licensed Apache-2.0. It adds 16 tokens to every session and 843 once invoked, about $0.0001 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 commands, from other repositories
dashboard
Phase 3 monitoring — System health, execution insights, and velocity analytics.
doctor
Check the health of a KARIMO installation, identify issues, and provide actionable recommendations.
run
Execute an approved PRD using feature branch workflow (v7.0). This command generates briefs, auto-reviews them, allows user iteration, and then orchestrates execution.
merge
Consolidate feature branch changes and create final PR to main. This completes the v5.0 feature branch workflow after all task PRs have been merged.
greptile-review
Execute the full Greptile review cycle on a PR, looping until score meets threshold or circuit breaker triggers.
update
Check for and apply KARIMO updates from GitHub releases.