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 tu11aa/squadrant --skill where-i-amgit clone --depth 1 https://github.com/tu11aa/squadrantWrote 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/tu11aa/squadrant/where-i-am)<a href="https://agentmods.dev/skills/tu11aa/squadrant/where-i-am"><img src="https://agentmods.dev/badge/skills/tu11aa/squadrant/where-i-am.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.00080 | $0.01249 |
| Opus 5 | $0.00040 | $0.00624 |
| Sonnet 5 | $0.00016 | $0.00250 |
| Haiku 4.5 | $0.00008 | $0.00125 |
Grade A, and why
where-i-am 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Where I Am
Answer "where am I on this project?" in a short, scannable report instead of a wall of text. Built for switching between long-running projects without losing the thread.
Read-only. This skill writes nothing and consumes nothing — pure orientation.
Output shape
Open with a one-line punchline, then the four sections in order:
**Right now →** <what you're actively doing / waiting on this moment, and your immediate next move>
## ✅ Done — and what it means
- <completed work> → <why it matters / what it unblocks>
## ⏳ In progress
- <work actively moving> — <state / owner: crew fixing, waiting on CI, mid-refactor>
## ▶️ Next
- ⬜ <the next not-yet-started step(s)>
## ⚠️ Watch
- <blockers, fragile state, gotchas, "don't forget", contradictions between sources>
Status markers — use inline when listing the steps of a track: ✅ done · ⏳ in progress · ⬜ not started.
Rules for the report:
Right now →is the most important line — the fast-orientation cue. Always include it; one line.- Bullets, not paragraphs. A handful per section, most-relevant first.
- Each Done bullet pairs what happened with why it matters (
→). A commit without significance is noise. - In progress vs Next: ⏳ is work already moving (a crew is on it, a branch is open, you're mid-edit); ⬜ Next is not yet started. Don't conflate them — the whole point is knowing what's live vs queued.
- Multi-track projects (e.g. a feature track + a bugfix track running in parallel): group bullets under bold track labels (
**Reorg track:**,**Bug-fix track:**) inside the sections. - If a section is genuinely empty, write
- — nothingrather than padding. - Synthesize, don't dump. Never paste raw git log / observation lists — distill them.
Source priority (current → durable)
Lead with the live session; use durable sources to fill gaps and cross-check.
- Current session context — primary. What this conversation has done, decided, and left open. Freshest signal, especially mid-task.
- claude-mem recent observations — the narrative across prior sessions (use the
mem-searchskill, or the recent-context already injected at session start). - Handoff + latest daily-log — explicit
nextSteps/blockedItems/decisionsandTomorrow/Blocked. - git — ground truth of where the code actually sits.
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 · 103 lines · 80 tokens per session scan A 787f4934e79c
where-i-am is a skill published in the GitHub repository tu11aa/squadrant (2 stars, last pushed yesterday), licensed MIT. It adds 80 tokens to every session and 1,249 once invoked, about $0.0004 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.