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 hoangsonww/AI-Agents-Orchestrator --skill inspect-historygit clone --depth 1 https://github.com/hoangsonww/AI-Agents-OrchestratorWrote 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/hoangsonww/ai-agents-orchestrator/inspect-history)<a href="https://agentmods.dev/skills/hoangsonww/ai-agents-orchestrator/inspect-history"><img src="https://agentmods.dev/badge/skills/hoangsonww/ai-agents-orchestrator/inspect-history/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/hoangsonww/ai-agents-orchestrator/inspect-history"><img src="https://agentmods.dev/badge/skills/hoangsonww/ai-agents-orchestrator/inspect-history.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.00031 | $0.00206 |
| Opus 5.5 | $0.00012 | $0.00082 |
| Sonnet 5 | $0.00006 | $0.00041 |
| Haiku 4.5 | $0.00003 | $0.00021 |
Grade A, and why
inspect-history 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.
What it actually says
Inspect History
Treat history inspection as read-only unless the user separately requests implementation.
- Get the active task with
ai_collaboration.current_task. - Use
ai_collaboration.search_historywith a narrow query derived from the user's question. - Expand a specific session with
ai_collaboration.session_eventsonly when needed. - Cross-check historical claims against current Git state with
ai_collaboration.changed_files. - Distinguish captured facts from inferences and note when a provider did not emit a field.
Do not dump full payloads by default. Request include_payload only when summaries omit necessary evidence; payloads are redacted but can still contain sensitive project content.
If MCP is unavailable, use bin/ai-collaboration search <query> and bin/ai-collaboration events.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 19 lines · 31 tokens per session scan A 7902571949a3
inspect-history is a skill published in the GitHub repository hoangsonww/AI-Agents-Orchestrator (84 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 206 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-09-21.
Other skills, from other repositories
github-review-pr
Review GitHub pull requests with detailed, multi-perspective code analysis using parallel subagents. Use this skill whenever the user wants to review a PR, asks for code review on a pull request, mentions "review PR", "check this PR", "look at pull request", or references a PR number or GitHub PR URL. Do NOT use for…
github-fix-issue
Fix GitHub issues end-to-end — analysis, branch creation, implementation, testing, and PR submission. Use whenever the user mentions fixing a GitHub issue, says "fix issue.
github-review-pr
Review a GitHub pull request with evidence-backed, multi-angle analysis and false-positive filtering. Use when the user asks to review, inspect, or check a pull request by number or URL. Not for local uncommitted changes.
memorix-git-memory
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.
respond-to-pr-comments
Respond to pull request review comments on GitHub or Azure DevOps Services. Reads review threads, validates each, proposes fixes or explanations, applies changes with user confirmation, and updates thread status via the platform's API. Use when the user wants to address PR feedback or resolve review threads.
apex-context-management
UTILITY SKILL — Two-mode context-window management. RUNTIME: artifact compression (full/summarized/minimal) used by orchestrator and codegen agents. AUDIT: post-mortem analysis of Copilot debug logs (token profiling, redundancy + hand-off gap detection) used by 11-Context Optimizer. WHEN: "context optimization"…