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.
git clone --depth 1 https://github.com/TechNickAI/ai-coding-configWrote 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/commands/technickai/ai-coding-config/session)<a href="https://agentmods.dev/commands/technickai/ai-coding-config/session"><img src="https://agentmods.dev/badge/commands/technickai/ai-coding-config/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/commands/technickai/ai-coding-config/session"><img src="https://agentmods.dev/badge/commands/technickai/ai-coding-config/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.00017 | $0.01065 |
| Opus 5.5 | $0.00007 | $0.00426 |
| Sonnet 5.5 | $0.00003 | $0.00213 |
| Haiku 4.5 | $0.00002 | $0.00106 |
Grade A, and why
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 25d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.claude/sessions/
├── active.json # Current session pointer
└── <session-id>/
├── metadata.json # Session info (name, created, branch, task)
├── context.md # Decisions, architecture, key context
├── progress.json # Completed steps, current step, blockers
└── files.json # Key files being worked on
Save current session state for later resumption.
-
Create session directory with timestamp ID
-
Capture metadata:
- Session name (from argument or auto-generate from task)
- Current git branch
- Timestamp
- Brief task description
-
Write context.md with:
- What we're building and why
- Key architectural decisions made
- Important constraints or requirements
- Current approach and alternatives considered
-
Write progress.json with:
- Completed steps
- Current step in progress
- Known blockers or open questions
- Next steps planned
-
Write files.json with:
- Key files being modified
- Files to review on resume
-
Update active.json to point to this session
Example:
/session save "auth-refactor"
/session resume [name|id]
Resume a saved session.
- Load session from
.claude/sessions/<id>/ - Read and present context.md summary
- Show progress status
- List key files for quick orientation
- Ask if ready to continue from last step
If no name/id provided, resume the active session (from active.json).
Example:
/session resume auth-refactor
/session resume # Resume active session
/session list
Show all saved sessions with:
- Session name and ID
- Creation date
- Branch
- Brief task description
- Progress status (X of Y steps)
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.
- 25d ago First seen · 169 lines · 17 tokens per session scan A 2e680dfa5e55
session is a command published in the GitHub repository TechNickAI/ai-coding-config (24 stars, last pushed 26d ago), licensed MIT. It adds 17 tokens to every session and 1,065 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-22.
Other commands, from other repositories
handoff
Emit a handoff artifact for this session (optionally specify a slug).
resume-from
Boot this session from a handoff artifact (slug, latest, or path).
capture
Run stackmemory capture to commit current work and generate a handoff prompt for the next session.
context
A project-context command that manages a .context directory containing decision notes, session logs, and history. It helps keep a record of why changes were made across Git branches and commits.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
advanced-code-review-context
Advanced Code Review Phase 2: Context Analysis - load previous reviews, PR history, declined items.