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/zhaono1/agent-playbook/auto-triggernpx skills add zhaono1/agent-playbook --skill auto-triggergit clone --depth 1 https://github.com/zhaono1/agent-playbookWrote 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/zhaono1/agent-playbook/auto-trigger)<a href="https://agentmods.dev/skills/zhaono1/agent-playbook/auto-trigger"><img src="https://agentmods.dev/badge/skills/zhaono1/agent-playbook/auto-trigger.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.00039 | $0.01135 |
| Opus 5 | $0.00019 | $0.00567 |
| Sonnet 5 | $0.00008 | $0.00227 |
| Haiku 4.5 | $0.00004 | $0.00113 |
Grade A, and why
auto-trigger 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 5d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto-Trigger Hooks
This skill defines trigger intent between skills. When a skill completes its workflow, a host runtime or agent may read this metadata, record a pending follow-up, and execute the next skill only when that action is supported and safe for the current session.
Hook Definitions
PRD Creation Chain
prd_complete:
triggers:
- skill: self-improving-agent
mode: background
condition: PRD file exists and is complete
- skill: session-logger
mode: auto
context: "PRD created for {feature_name}"
prd_implemented:
triggers:
- skill: session-logger
mode: auto
context: "Implemented PRD: {feature_name}"
Implementation Chain
implementation_complete:
triggers:
- skill: code-reviewer
mode: ask_first
message: "Implementation complete. Run code review?"
- skill: create-pr
mode: ask_first
condition: user_requested_submission
Session Management
session_start:
auto_triggers:
- skill: session-logger
action: create_session_file
session_end:
auto_triggers:
- skill: session-logger
action: update_session_file
Hook Format in Skills
To add auto-trigger capability to a skill, add to its front matter:
---
name: my-skill
description: Skill description
allowed-tools: Read, Write, Edit
hooks:
before_start:
- trigger: session-logger
mode: auto
context: "Start {skill_name}"
after_complete:
- trigger: self-improving-agent
mode: background
- trigger: session-logger
mode: auto
on_error:
- trigger: self-improving-agent
mode: background
---
Implementation Guide
When a skill completes its workflow:
- Check
hooksin its own front matter (before_start,after_complete,on_error,on_progress) - For each hook:
- If
mode: auto, record or run a low-risk follow-up only when the host runtime supports it - If
mode: background, record a non-blocking follow-up; do not mutate durable files silently - If
mode: ask_first, ask user before triggering - If
condition:exists, check it first
- If
- Pass context to the triggered skill
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.
- 5d ago First seen · 181 lines · 39 tokens per session scan A 91422d086561
auto-trigger is a skill published in the GitHub repository zhaono1/agent-playbook (77 stars, last pushed 10d ago), licensed MIT. It adds 39 tokens to every session and 1,135 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…