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 hooks/uta2000/feature-flow/session-startgit clone --depth 1 https://github.com/uta2000/feature-flowGrade A, and why
SessionStart 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 yesterday.
A static scan of the commands this hook runs, not an audit. A hook is shell that executes on your machine at the event it names, which is why every command in it is printed with what was found.
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 — 20 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"SessionStart": [
{
"hooks": [
{
"type": "command",
"command": "if [ -f .feature-flow.yml ]; then echo 'FEATURE-FLOW DEVELOPMENT ACTIVE: Use start: to begin any non-trivial work — it orchestrates the full lifecycle (design → verify → implement → ship). Rules: (1) Every task in an implementation plan MUST include **Acceptance Criteria:** with machine-verifiable - [ ] items. After writing a plan, run verify-plan-criteria. (2) Before claiming any task is complete, run verify-acceptance-criteria to mechanically check all criteria against the codebase. (3) Before writing new code, query Context7 docs for current patterns — library IDs are in .feature-flow.yml under context7. (4) PreToolUse hooks deny (block) Write/Edit calls containing any types, as any, or empty catch blocks — fix before writing; Task/Agent dispatches missing an explicit model parameter are denied the same way. console.log/debug is a PostToolUse advisory warning, not a block, and is allowed during TDD. (5) Stop hook runs tsc, lint, type-sync, and test checks and blocks session end on failures; per-file lint warnings from the PostToolUse hook remain advisory and do not block. (6) Tool API: Skill tool params are skill and args (NOT skill_name/arguments). Deferred tools (TaskCreate, TaskUpdate) must be loaded via ToolSearch before use. See references/tool-api.md for all tool syntax. Type \"start: <description>\" or \"start: <description> --yolo\" to begin.'; if ! grep -q 'context7:' .feature-flow.yml 2>/dev/null; then echo ''; echo 'UPGRADE NOTICE (v1.6.0): Your .feature-flow.yml is missing the context7 field. Run start: to auto-detect Context7 library IDs for your stack, or add them manually. New in v1.6.0: Context7 doc lookups, coding-standards.md, Study Existing Patterns step, Self-Review step, anti-pattern blocking hooks. See CHANGELOG.md for details.'; fi; else echo 'FEATURE-FLOW is installed. It helps you build features without mid-implementation surprises byWhat 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.
- yesterday First seen · 20 lines scan A 8c75c5034b85
SessionStart is a hook published in the GitHub repository uta2000/feature-flow (4 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: a hook is shell that never enters the context. 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 hooks, from other repositories
PostToolUse
Runs after a tool call finishes for Write and Edit tool calls, executing format_and_lint.sh. From supabase/supabase.
SessionStart
Runs when a session starts on startup, executing install_pkgs.sh. From supabase/supabase.
SessionStart
Runs when a session starts, executing on-start.js via node. From google-gemini/gemini-cli.
PreToolUse
Runs before the agent uses a tool, executing pre-write.sh and pre-bash.sh (2 commands). From anthropics/claude-cookbooks.
SessionStart
Runs when a session starts, executing session-start.sh. From anthropics/claude-cookbooks.
SessionStart
Runs when a session starts on startup, clear and compact, executing run-hook.cmd. From obra/superpowers.