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 g-hyeong/MCP-AidFlow --skill reportgit clone --depth 1 https://github.com/g-hyeong/MCP-AidFlowWrote 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/g-hyeong/mcp-aidflow/report)<a href="https://agentmods.dev/skills/g-hyeong/mcp-aidflow/report"><img src="https://agentmods.dev/badge/skills/g-hyeong/mcp-aidflow/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/g-hyeong/mcp-aidflow/report"><img src="https://agentmods.dev/badge/skills/g-hyeong/mcp-aidflow/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.00013 | $0.00386 |
| Opus 5.5 | $0.00005 | $0.00154 |
| Sonnet 5.5 | $0.00003 | $0.00077 |
| Haiku 4.5 | $0.00001 | $0.00039 |
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 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
Generate a completion report for the most recently archived session.
Steps
- Find the latest directory in
.aidflow/history/(sorted by name, newest first) - Read
meta.jsonfrom that directory to get session metadata - Read
plan.mdfrom that directory (if exists) - Gather git commits for the session period:
- Use
created_atandcompleted_atfrom meta.json as the time range - Run:
git log --oneline --after="{created_at}" --before="{completed_at}" - If no completed_at, use current time as the end
- Use
- Read the changed files listed in meta.json and briefly review each
- Write
report.mdin the history directory
report.md Format
# {Session Name} - Report
## Summary
{1-2 line summary of what was accomplished}
## Plan Completion
{Plan items and their completion status, if plan existed}
## Changed Files
| File | Change Type | Description |
|------|-------------|-------------|
| path/to/file | modified/new/deleted | Brief description |
## Key Decisions
{Important technical decisions made during the work}
## Issues & Observations
{Any issues found, edge cases discovered, or observations for future reference}
## Duration
- Started: {created_at}
- Completed: {completed_at}
- Commits: {number of commits in range}
Notes
- If the history directory is empty, inform the user to run
session completefirst - Focus on factual reporting, not speculation
- Keep descriptions concise but informative
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 · 55 lines · 13 tokens per session scan A a53db80347d4
report is a skill published in the GitHub repository g-hyeong/MCP-AidFlow (0 stars, last pushed 8mo ago), licensed MIT. It adds 13 tokens to every session and 386 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-31.
report compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| reportg-hyeong/MCP-AidFlow | Skill | 0 | 8mo ago | MIT | A | 13 | Claude Code |
| imagegenopenai/codex | Skill | 134k | today | Apache-2.0 | A | 113 | Codex |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | yesterday | MIT | A | 200 | Claude Code, Codex |
| playwright-climicrosoft/playwright | Skill | 100k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| browser-automationopenclaw/openclaw | Skill | 394k | today | MIT | A | 36 | Claude Code |
| systematic-debuggingobra/superpowers | Skill | 314k | 4d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |