Borrowing it
Nothing to install: this file belongs to suuus/ape-context. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/suuus/ape-context/main/.github/skills/context-history/SKILL.mdgit clone --depth 1 https://github.com/suuus/ape-contextWrote 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/suuus/ape-context/context-history)<a href="https://agentmods.dev/skills/suuus/ape-context/context-history"><img src="https://agentmods.dev/badge/skills/suuus/ape-context/context-history.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.1 | $0.00019 | $0.01740 |
| Opus 5 | $0.00010 | $0.00870 |
| Sonnet 5 | $0.00004 | $0.00348 |
| Haiku 4.5 | $0.00002 | $0.00174 |
Grade A, and why
context-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 7d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze the user's Copilot session history to extract behavioural patterns that reveal implicit intent, recurring workflows, and areas of focus. This complements documentation-based analysis — docs tell you what the team says they value, history tells you what they actually do.
Data Source
Use the session_store_sql tool to query the cloud session store. This contains all past Copilot sessions with:
- sessions — id, repository, branch, summary, timestamps
- turns — user messages and assistant responses per session
- session_files — files edited/created per session
- session_refs — commits, PRs, and issues linked to sessions
Use scope: "personal" for individual patterns, scope: "repository" for team-wide patterns when the user wants a broader view.
Consent Gate (MANDATORY — run first)
Before running any queries or asking about scope, you MUST ask the user for explicit permission using ask_user. Do NOT proceed until the user grants consent.
Present the following information clearly:
What: This skill reads your Copilot session history from the last 30 days — session summaries, files you edited, repos you worked in, issues/PRs you referenced, and the messages you sent to Copilot.
How: It queries a cloud session store using read-only SQL. Nothing is modified, created, or shared externally. The data stays in this conversation. When using "repository" scope, only aggregate patterns are analysed — individual messages from other contributors are not surfaced.
Why: By understanding what you actually work on (not just what's documented), the context wizard can generate more accurate Copilot instructions, detect workflow gaps, and surface patterns you might not notice yourself — like frequently edited files, cross-repo coupling, or missing ticket references.
Use ask_user with a boolean consent field. Example:
message: |
🔒 **Session history analysis — permission required**
This skill will **read your Copilot session history** from the last 30 days to discover work patterns and recurring workflows.
**What is accessed:**
• Session summaries and timestamps
• Files you edited or created
• Repositories you worked in
• Issues and PRs referenced in sessions
• Messages you sent to Copilot (truncated to 200 chars)
**How:** Read-only SQL queries against the cloud session store. Nothing is modified or shared.
**Why:** To generate better Copilot instructions by understanding your actual workflow — not just what's documented.
requestedSchema:
properties:
consent:
type: boolean
title: "Allow session history analysis?"
description: "Grant permission to read your session history for pattern analysis."
default: false
required: [consent]
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.
- 7d ago First seen · 198 lines · 19 tokens per session scan A 830bd83f7eec
context-history is a skill published in the GitHub repository suuus/ape-context (2 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 1,740 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…