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 jstoup111/ai-conductor --skill stack-landgit clone --depth 1 https://github.com/jstoup111/ai-conductorWrote 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/jstoup111/ai-conductor/stack-land)<a href="https://agentmods.dev/skills/jstoup111/ai-conductor/stack-land"><img src="https://agentmods.dev/badge/skills/jstoup111/ai-conductor/stack-land/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/jstoup111/ai-conductor/stack-land"><img src="https://agentmods.dev/badge/skills/jstoup111/ai-conductor/stack-land.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.00047 | $0.00716 |
| Opus 5.5 | $0.00019 | $0.00286 |
| Sonnet 5.5 | $0.00009 | $0.00143 |
| Haiku 4.5 | $0.00005 | $0.00072 |
Grade A, and why
stack-land 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 2d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Guide an operator through opening a reviewer-edit landing on the child that owns the affected code. This is an operator-only workflow: it never runs during a dispatched step and never opens a landing without the person's explicit confirmation.
Procedure
-
Get the feature slug, the exact paths changed by the reviewer, and the reason for the landing. Do not infer ownership from a branch name, a title, or the current checkout.
-
Before proposing any child, run the ownership query for every affected path:
ai-conductor stack owners --slug <slug> --path <path> [--path <path> ...]Preserve the output as the ownership evidence. It names each owning child with its position, branch, and slice title.
-
Propose the lowest-position child that owns the code being changed. State the proposed child number, its slice title, and the relevant
stack ownersevidence. If the change needs code that first exists in a higher child, propose that higher child instead and explain the prerequisite from the same evidence; do not silently carry a lower child upward. -
Ask for explicit confirmation before changing anything. For example: “The proposed landing is child
<n>—<slice title>; evidence:<owners output>. Shall I open this landing?” Do not run a command until the person confirms this proposed child and supplies or confirms the reason. -
Only after confirmation, open the landing with the confirmed child:
ai-conductor stack land --slug <slug> --child <n> --reason "<why>"Add
--carry <n>only when the operator has explicitly confirmed the carried child and the command's ownership evidence establishes that it is required. -
If the person rejects the proposal, do not run
stack landfor that child. Ask which child they want to use instead, show its title and the ownership evidence, and obtain a new explicit confirmation before any landing command.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 82 lines · 47 tokens per session scan A 8e38b992d322
stack-land is a skill published in the GitHub repository jstoup111/ai-conductor (7 stars, last pushed yesterday), licensed Apache-2.0. It adds 47 tokens to every session and 716 once invoked, about $0.0002 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-10-28.
Other skills, from other repositories
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…