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 aget-framework/template-advisor-aget --skill aget-describe-sessiongit clone --depth 1 https://github.com/aget-framework/template-advisor-agetWrote 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/aget-framework/template-advisor-aget/aget-describe-session)<a href="https://agentmods.dev/skills/aget-framework/template-advisor-aget/aget-describe-session"><img src="https://agentmods.dev/badge/skills/aget-framework/template-advisor-aget/aget-describe-session/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/aget-framework/template-advisor-aget/aget-describe-session"><img src="https://agentmods.dev/badge/skills/aget-framework/template-advisor-aget/aget-describe-session.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.00027 | $0.01243 |
| Opus 5 | $0.00014 | $0.00622 |
| Sonnet 5 | $0.00005 | $0.00249 |
| Haiku 4.5 | $0.00003 | $0.00124 |
Grade A, and why
aget-describe-session 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 10d 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.
This is a copy
100% identical to aget-describe-session — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/aget-describe-session
Generate a readable narrative summary from structured session data. Converts table-heavy session artifacts into prose optimized for human scanning.
Purpose
AGET sessions produce structured output (frontmatter, tables, bullet lists, commit logs) that is machine-parseable but hard for humans to read at a glance. This skill transforms structured session artifacts into narrative prose that conveys the same information in a form a principal or collaborator can scan quickly.
Evidence: Principal feedback (2026-04-10) — "this report is hard to read" on a 7-row table summarizing 7 sequential steps, where 2 lines of prose conveyed the same information more clearly. Tables are effective for comparison data (rubric scores, deployment status). Prose is effective for sequential narratives (what happened, what was decided, what's next).
Input
$ARGUMENTS
Parameters (all optional):
| Parameter | Values | Default | Purpose |
|---|---|---|---|
--source |
Session file path or current |
current |
Which session to describe |
--length |
brief, standard, detailed |
standard |
Narrative depth |
Examples:
/aget-describe-session— Describe current session in standard length/aget-describe-session --source sessions/SESSION_2026-04-10_1400.md— Describe a prior session/aget-describe-session --length brief— Short 1-2 paragraph summary of current session
Execution
Step 1: Resolve Source
Determine the session to describe:
| Source | Resolution |
|---|---|
current (default) |
Synthesize from conversation context — what was worked on, decisions made, artifacts produced |
| Session file path | Read the specified session record from sessions/ |
latest |
Find most recent sessions/SESSION_*.md by date |
Verify: Confirm source material exists. If describing current session, verify there is meaningful work to describe (not just wake-up).
Step 2: Extract Narrative Elements
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.
- 10d ago First seen · 112 lines · 27 tokens per session scan A dcc00049e411
aget-describe-session is a skill published in the GitHub repository aget-framework/template-advisor-aget (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 27 tokens to every session and 1,243 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to aget-describe-session, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
tt-sidebar
Open a live Token Tracker sidebar for only the current Codex session in a right-side terminal split at one-third width. Use when the user explicitly invokes $tt-sidebar or asks to monitor the current Codex session beside its terminal pane.
tt-sidebar
Open a live Token Tracker sidebar for only the current Kimi Code session in a right-side terminal split at one-third width. Use when the user explicitly invokes /skill:tt-sidebar or asks to monitor the current session beside its terminal pane.
pir-action-tracker
Parses Post-Incident Review (PIR) pages in a Confluence space, fetches live status from referenced Jira tickets, updates action item tables with current status and due dates, marks completed PIRs with a visual closure panel, and surfaces any overdue actions for follow-up. Designed for Customer Success, Support, and…
perseus
Use when you need a bounded, local Perseus context render before an assistant reads project state. Perseus resolves selected workspace inputs such as git, services, sessions, and task notes into markdown. Use for deterministic session starts, workspace audits, and explicit context handoffs.
raindrop
Manage Raindrop.io bookmarks, collections, tags, and highlights via API. Use when user mentions raindrop, bookmarks, saving links, organizing URLs, bookmark collections, or web highlights.
metagit-cli
CLI-only shortcuts for metagit agents — workspace catalog, discovery, prompts, sync, layout, and config. Use instead of MCP or HTTP API when operating from a shell or agentmode session.