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 pomagrenate/ice_age --skill iceage-exportgit clone --depth 1 https://github.com/pomagrenate/ice_ageWrote 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/pomagrenate/ice_age/iceage-export)<a href="https://agentmods.dev/skills/pomagrenate/ice_age/iceage-export"><img src="https://agentmods.dev/badge/skills/pomagrenate/ice_age/iceage-export/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/pomagrenate/ice_age/iceage-export"><img src="https://agentmods.dev/badge/skills/pomagrenate/ice_age/iceage-export.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.00073 | $0.00517 |
| Opus 5.5 | $0.00029 | $0.00207 |
| Sonnet 5.5 | $0.00015 | $0.00103 |
| Haiku 4.5 | $0.00007 | $0.00052 |
Grade A, and why
iceage-export 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 1mo 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
Export current conversation to a markdown file. Reconstruct from visible context.
Invocation
/iceage-export → chat-export-YYYY-MM-DD.md (current dir)
/iceage-export <filename> → exact path/name given
/iceage-export <filename> --no-code → strip code blocks from output
What to Export
Reconstruct the full visible conversation in order:
- Every user message — exact wording, no paraphrasing
- Every assistant response — full content, preserve all code blocks, lists, tables
- Tool calls — include only if they produced user-visible output (e.g. file reads, search results). Skip internal plumbing (file existence checks, etc.)
- System context visible to user — skip hidden hook injections
Output Format
# Chat Export — YYYY-MM-DD HH:MM
**Session:** <working directory or project name if known>
---
## User
<exact user message text>
---
## Assistant
<full assistant response>
---
## User
...
Rules:
- Preserve all code blocks exactly — language tag, indentation, content unchanged
- Preserve all markdown (headings, bullets, tables, bold, links)
- Timestamp in filename uses local date:
chat-export-2026-04-26.md - If file already exists, append
_2,_3etc — never overwrite silently - Confirm filename to user after writing:
Exported: <path>
What NOT to Include
- Session hook injections (ICEAGE MODE ACTIVE banners, system reminders)
- Internal tool calls that weren't user-visible (stat checks, glob searches with no result shown)
- Your own internal reasoning or
<thinking>blocks - Duplicate content (don't include both a tool call and its already-rendered output)
Boundaries
One-shot operation. Does not modify conversation. Does not affect iceage mode. "stop iceage-export": cancel and do nothing.
After writing the file, report: Exported: <absolute path> (<N> exchanges)
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.
- 1mo ago First seen · 75 lines · 73 tokens per session scan A 8ca2f5e87384
iceage-export is a skill published in the GitHub repository pomagrenate/ice_age (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 73 tokens to every session and 517 once invoked, about $0.0003 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.
Other skills, from other repositories
code-to-diagram
Analyze codebases and automatically generate architecture diagrams, flowcharts, and org charts. Uses AST parsing to map import dependencies for Python, JS/TS, Go, and Java, outputting Mermaid or SVG files. Triggered when users ask to visualize code architecture, understand dependencies, draw a flowchart, or create a…
token-saver
Reduce avoidable token and API cost through task-aware model selection, context hygiene, concise responses, and disciplined tool use. Apply as an advisory policy on every turn. Actual savings vary by agent, model, provider, cache behavior, and workload; measure results instead of assuming a fixed percentage.
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
legal-hold
Issue, refresh, release, or report on legal holds — drafts the hold notice as .docx, updates legalhold fields in log.yaml, and calendars the next refresh. Use when the user says "issue a hold", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.