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 Justinmendezai/The-Adam-Repo --skill session-stewardgit clone --depth 1 https://github.com/Justinmendezai/The-Adam-RepoWrote 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/justinmendezai/the-adam-repo/session-steward)<a href="https://agentmods.dev/skills/justinmendezai/the-adam-repo/session-steward"><img src="https://agentmods.dev/badge/skills/justinmendezai/the-adam-repo/session-steward/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/justinmendezai/the-adam-repo/session-steward"><img src="https://agentmods.dev/badge/skills/justinmendezai/the-adam-repo/session-steward.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.00057 | $0.01615 |
| Opus 5 | $0.00028 | $0.00807 |
| Sonnet 5 | $0.00011 | $0.00323 |
| Haiku 4.5 | $0.00006 | $0.00161 |
Grade A, and why
session-steward 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 12d 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.
session-steward
Meta orchestrator = memory manager, not implementer. Long-term continuity lives in agent-control/, orchestration-runs/, git, and tests — not in one endless chat.
Use this skill after a build orchestrator finishes a bounded cycle (or when the human asks for the next brief).
Explicit non-goals
- No edits to production
src/,app/, etc. - No
dispatch-builder/dispatch-parallel. - No slice spec or test file changes.
- Minimal reasoning: compress, file, link — do not replan the whole product.
When to use
- A build orchestrator completed one objective in
agent-control/active-sprint.md(or stopped with a clear blocker). - Token pressure: you want a fresh build orchestrator with a tight brief.
- After
e2e-acceptanceor a major test pass — roll results intoagent-control/test-status.md.
Inputs (read-only)
agent-control/active-sprint.md,agent-control/current-state.md,agent-control/completed-work.mdagent-control/slice-status.md— final registry stateagent-control/human-queue.md— open operator itemsagent-control/rework-ledger.md— agentic review/rework rows this run (create empty template if missing)- Latest
orchestration-runs/run-*folder (if any) scratch/last-run.md,scratch/handoff/primer-*.md(most recent optional)slices/README.md,plan/CONTEXT.md(one screen each)scratch/e2e-acceptance.mdorscratch/run-results/e2e-*.jsonif presentpacket/PACKET.mdverification/e2efor test layer names
Context budget (soft)
| Output | Target |
|---|---|
next-orchestrator-brief.md |
~20k–30k characters; bullets first |
orchestration-runs/run-NNN/summary.md |
~2k–4k characters |
| Bullet lists | 10 bullets max for “what happened” and “what’s next” |
Do not rely on live token meters — use character caps and short bullets.
Workflow
1. Allocate run id
- Pick the next folder:
orchestration-runs/run-003/(zero-pad or use date — match existing convention in the repo). - If the build orchestrator already created this folder and filled files, update in place instead of duplicating.
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.
- 12d ago First seen · 103 lines · 57 tokens per session scan A dd2646aac04b
session-steward is a skill published in the GitHub repository Justinmendezai/The-Adam-Repo (12 stars, last pushed 18d ago), licensed Apache-2.0. It adds 57 tokens to every session and 1,615 once invoked, about $0.0003 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
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…
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.
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…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.