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 d0hx4n2503/Agent-Skills --skill loop-megit clone --depth 1 https://github.com/d0hx4n2503/Agent-SkillsWrote 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/d0hx4n2503/agent-skills/loop-me)<a href="https://agentmods.dev/skills/d0hx4n2503/agent-skills/loop-me"><img src="https://agentmods.dev/badge/skills/d0hx4n2503/agent-skills/loop-me/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/d0hx4n2503/agent-skills/loop-me"><img src="https://agentmods.dev/badge/skills/d0hx4n2503/agent-skills/loop-me.svg" alt="Reviewed on agentmods" width="80" height="20"></a>The source is not reproduced here
Licensed Apache-2.0
The repository is licensed Apache-2.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 1mo ago First seen · 1 lines e3b0c44298fc
loop-me is a skill published in the GitHub repository d0hx4n2503/Agent-Skills (2 stars, last pushed 2mo ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. It was not scanned, because the body is not available under its licence. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
story-implementation-planner
Create a constraint-aware implementation plan from a Ready Story Card and sufficiently evidenced Repo Context. Use when the requested artifact is the plan itself; use story-to-plan-orchestrator for multi-stage preparation, packet completion, resumption, or validation. Avoid story drafting, repo scouting, and direct…
story-repo-scout
Inspect a repository for story-specific implementation evidence, applicable decisions, validation prior art, and bounded planning-critical external primary sources, then produce compact Repo Context. Use for pre-implementation file discovery and greenfield path grounding; use tester-mindset for test strategy and avoid…
context-engineering
Workflow for context packets, context audits, compaction, handoffs, session memory, and deciding what AI-agent context to load, retrieve, trim, summarize, refresh, or omit. Use for context rot, context flooding, stale or missing context, task switching, and long-running agent sessions. Do not use when prompt wording…
setup-playwright
Use when adding, extending, or repairing a repo-owned Playwright test harness across Node Playwright Test, Playwright Pytest, or .NET/Java test frameworks. Also use when explicitly persisting @playwright/cli developer tooling, or adding or regenerating Playwright Test Agent definitions for a compatible Node Playwright…
story-to-plan-orchestrator
Coordinate multi-stage story-to-plan preparation across story-clarifier, story-repo-scout, and story-implementation-planner. Use for complete implementation-ready handoffs, two or more missing stages, split-slice selection, partial-packet resumption, consistency validation, or stale-stage recovery before coding; use a…
development-contract-system
Build a portable change-contract system for any repository. Use when creating or porting a repository workflow based on tracked feature records, lifecycle directories, a policy file, a checker, a lifecycle transition helper, and aligned docs/tests.