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 agentmods add skills/ahmadulhoq/agentskel/session-startnpx skills add ahmadulhoq/agentskel --skill session-startgit clone --depth 1 https://github.com/ahmadulhoq/agentskelWrote 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/ahmadulhoq/agentskel/session-start)<a href="https://agentmods.dev/skills/ahmadulhoq/agentskel/session-start"><img src="https://agentmods.dev/badge/skills/ahmadulhoq/agentskel/session-start.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 | $0.00043 | $0.02891 |
| Opus 5 | $0.00022 | $0.01445 |
| Sonnet 5 | $0.00009 | $0.00578 |
| Haiku 4.5 | $0.00004 | $0.00289 |
Grade A, and why
session-start 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 3d 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Start Procedure
Execute every step below in order. Do not skip steps. Do not start any user task until this procedure is complete.
Step 1 — Check memory mount
- Check whether
.memory/exists in the repo root. - Exists → pull the latest memory from remote before reading anything:
If the pull fails (e.g. network unavailable, diverged history), warn the user but proceed — stale memory is better than no memory. Then continue to Step 2.git -C .memory pull --ff-only origin ai-memory 2>/dev/null || true - Does NOT exist → STOP. Do not start any task. Instead:
- Run
git branch -r | grep origin/ai-memory - Found → tell the user:
"This project has AI memory but it's not mounted. Run
./scripts/install-agent.sh(orgit worktree add .memory ai-memory) to load it, then restart this session." - Not found → tell the user:
"This project has no AI memory. A tech lead needs to run the
setup-skeletonworkflow first. See the agentskel README for setup instructions." - End session. Do not attempt any work without memory files.
- Run
Step 1b — Link external skills (auto-recover after pull)
External skill packs (e.g. Google's android/skills) install into a shared per-machine store at ~/.agentskel/skills/ and are surfaced to each project via gitignored symlinks under .agents/skills/. After a teammate pulls a sync that introduced new external skill entries — or after a fresh clone — the manifest exists but the symlinks do not yet. Detect and auto-recover before reading anything else.
- Check whether
.agents/skills/.gitignoreexists. - Does not exist → no external skills configured for this project. Skip to Step 2.
- Exists → read the manifest (non-comment, non-blank lines are external skill directory names). For each entry, check whether
.agents/skills/[name]exists as a symlink.- If every entry resolves to an existing symlink → skip to Step 2.
- If any entry is missing → run
bash scripts/install-agent.shonce. The script is idempotent: it re-pulls.memory/, then for each manifest entry tries to create a symlink pointing into~/.agentskel/skills/. Surface any "shared store missing pack" warnings the script prints to the user, and offer to run theupdate-external-skillsworkflow now if a pack needs installing.
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.
- 3d ago First seen · 195 lines · 43 tokens per session scan A d27f1c69de0e
session-start is a skill published in the GitHub repository ahmadulhoq/agentskel (13 stars, last pushed 19d ago), licensed MIT. It adds 43 tokens to every session and 2,891 once invoked, about $0.0002 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-09-02.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…