Borrowing it
Nothing to install: this file belongs to GeoloeG-IsT/agents-reverse-engineer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/GeoloeG-IsT/agents-reverse-engineer/main/.claude/skills/are-specify/SKILL.mdgit clone --depth 1 https://github.com/GeoloeG-IsT/agents-reverse-engineerWrote 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/geoloeg-ist/agents-reverse-engineer/are-specify)<a href="https://agentmods.dev/skills/geoloeg-ist/agents-reverse-engineer/are-specify"><img src="https://agentmods.dev/badge/skills/geoloeg-ist/agents-reverse-engineer/are-specify.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.00015 | $0.00448 |
| Opus 5 | $0.00008 | $0.00224 |
| Sonnet 5 | $0.00003 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
are-specify 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 8d 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.
What it actually says
Generate a project specification from existing AGENTS.md documentation.
Steps
-
Read version: Read
.claude/ARE-VERSION→ store as$VERSION. Show the user:agents-reverse-engineer v$VERSION -
Run the specify command in the background using
run_in_background: true:npx agents-reverse-engineer@$VERSION specify --backend claude $ARGUMENTS -
Monitor progress by polling the latest progress log:
- Wait ~15 seconds (use
sleep 15in Bash), then use Glob to find the latest.agents-reverse-engineer/progress-*.logfile, and Read it (use theoffsetparameter to read only the last ~20 lines for long files) - Show the user a brief progress update
- Check whether the background task has completed using
TaskOutputwithblock: false - Repeat until the background task finishes
- Important: Keep polling even if no progress log exists yet (the command takes a few seconds to start writing)
- Wait ~15 seconds (use
-
On completion, read the full background task output and summarize:
- Number of AGENTS.md files collected
- Output file(s) written
This collects all AGENTS.md files, synthesizes them via AI, and writes a comprehensive project specification.
If no AGENTS.md files exist, it will auto-run generate first.
Options:
--dry-run: Show input statistics without making AI calls--output <path>: Custom output path (default: specs/SPEC.md)--multi-file: Split specification into multiple files--force: Overwrite existing specification--debug: Show AI prompts and backend details--trace: Enable concurrency tracing to.agents-reverse-engineer/traces/
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.
- 8d ago First seen · 44 lines · 15 tokens per session scan A fc04e7bc68db
are-specify is a skill published in the GitHub repository GeoloeG-IsT/agents-reverse-engineer (20 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 448 once invoked, about $0.0001 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
wttr-weather
Weather via wttr.in GET (no key). Use for weather/forecast; prefer os.http.request.
jk
Manage Jenkins controllers with jk, including jobs, runs, logs, artifacts, credentials, nodes, queues, and plugins.
repo-health-check
Use when auditing a repo before changes to find the smallest safe PR, quality risks, stale docs, missing tests, ignored-file gaps, or agent setup issues. Best first skill for unfamiliar codebases.
architecture-review
Use for clean architecture, modular monoliths, hexagonal boundaries, service boundaries, data flow, dependency direction, ADRs, or large feature planning.
hatch3r-board-refresh
Regenerates the living board overview dashboard from current board state. Scans all open issues, computes health metrics, and updates the meta:board-overview issue.
hatch3r-qa-path
Produces a human-run manual QA test path from a PR, branch diff, or uncommitted working tree — a risk-ordered table of steps, expected results, and automated-coverage references plus a shippability sign-off. Rows are auto-proven via delegated verification sub-agents before emission, so the human walks only what…