agentmods.dev

TRIGGERS

TRIGGERS is a command for Claude Code from Phoenix0531-sudo/tidy-skill. It costs 0 tokens per session (694 once invoked), scanned A, original, MIT.

A set of documentation phrases and slash-style command names that tell a host which repository-hygiene workflow to run. They are instructions for mapping commands, not a program or server.

In plain words
What is it for?
Use them to run read-only hygiene checks, score a repository, inspect suspicious agent files, check where a new file belongs, review local storage growth, or enforce a minimum hygiene score in continuous integration.
Why use it?
They give teams consistent ways to request checks without needing to remember each script or workflow name.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md). Also seen: mentions AGENTS.md; mentions Codex.

not rated 18repo 2mo ago A scan 0 tokens original MIT

Good fit Use them to run read-only hygiene checks, score a repository, inspect suspicious agent files, check where a new file belongs, review local storage growth, or enforce a minimum hygiene score in continuous integration.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/phoenix0531-sudo/tidy-skill/triggers
View source ↗ Phoenix0531-sudo/tidy-skill phoenix0531-sudo.github.io
Install

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.

Clone the repo
git clone --depth 1 https://github.com/Phoenix0531-sudo/tidy-skill

Made for: Claude Code.

Wrote 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.

agentmods badge for TRIGGERS

README.md
[![agentmods](https://agentmods.dev/badge/commands/phoenix0531-sudo/tidy-skill/triggers/github.svg)](https://agentmods.dev/commands/phoenix0531-sudo/tidy-skill/triggers)
Your own site
<a href="https://agentmods.dev/commands/phoenix0531-sudo/tidy-skill/triggers"><img src="https://agentmods.dev/badge/commands/phoenix0531-sudo/tidy-skill/triggers/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.

agentmods 80×15 button for TRIGGERS

Your own site · 80×15
<a href="https://agentmods.dev/commands/phoenix0531-sudo/tidy-skill/triggers"><img src="https://agentmods.dev/badge/commands/phoenix0531-sudo/tidy-skill/triggers.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 694 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00694
Opus 5.5 $0.00000 $0.00278
Sonnet 5.5 $0.00000 $0.00139
Haiku 4.5 $0.00000 $0.00069

Measured 2mo ago against content hash ba4671e37a20, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

TRIGGERS 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 2mo 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.

skills/tidy-skill/commands/TRIGGERS.md · 45 lines

How it starts

The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Trigger phrases / slash-style commands

These are documentation triggers for hosts that map natural language or slash commands to skills. They do not install a runtime server.

Command stubs (markdown playbooks hosts can map):

Trigger Intent Preferred tool
/tidy or "run tidy-skill" Full local hygiene pass (read-only first) score + artifact audit
/tidy-score or "repo hygiene score" Score current repo 0-100 score_repo_hygiene.py
/tidy-doctor or "tidy doctor" Package + hygiene one-shot gate tidy_doctor.py
/classify-path or "should I create this file" Class A–E path check before write classify_artifact.py
/tidy-gate or "hygiene score gate" Fail CI if score below policy min hygiene_snapshot.py gate
/audit-artifacts or "scan agent files" List suspicious root process files audit_agent_artifacts.py
/audit-env or "why is my disk growing" Local cache / WSL / model footprint map audit_dev_environment.py / .ps1
/audit-workspace Multi-repo parent folder audit audit_workspace_hygiene.py
/tidy-clean-preview DryRun cleanup preview only clean-agent-artifacts.ps1 -DryRun
/tidy-hooks-check End-of-task read-only stop check hooks/stop-hygiene-check.py

Canonical prompts

  1. "Score this repository's agent hygiene and list suspicious root Markdown."
  2. "Audit agent artifacts under the current repo; do not delete anything."
  3. "Map local package and model caches; separate safe suggestions from risky operations."
  4. "Scan every Git repo under D:/Projects for plan.md/todo.md pollution."
  5. "Preview cleanup of expired .agent_tmp files in DryRun mode."
  6. "Install tidy-skill into Claude and Codex skill folders (preview first)."
  7. "Install AGENTS.md hygiene rules into this project without overwriting unless forced."
  8. "Before you finish, run the read-only stop hygiene check."
  9. "Run tidy doctor on this repo and fail if score is below 80."
  10. "Classify whether plan.md at the root is allowed before creating it."
  11. "Save a hygiene snapshot, then gate CI on .tidy-skill.json min_score."

Read the full file on GitHub · 45 lines

Changes

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.

  1. 2mo ago First seen · 45 lines · 0 tokens per session scan A ba4671e37a20

Subscribe to this mod's changes

TRIGGERS is a command published in the GitHub repository Phoenix0531-sudo/tidy-skill (18 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 694 tokens. 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.

agent-skillsai-agentcodespacesskillskillstidy-data
Related

TRIGGERS compared with commands from other repositories

TRIGGERS next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
TRIGGERSPhoenix0531-sudo/tidy-skillCommand182mo agoMITA0Claude Code
drupalsiva01c/claude-pluginsCommand16yesterdayMITA10Claude Code
automode-editobeone/claude-skillsCommand42d agoMITB43Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
analyzegithub/spec-kitCommand148kyesterdayMITA26Claude Code