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 commands/nguyenthienthanh/aura-frog/projectgit clone --depth 1 https://github.com/nguyenthienthanh/aura-frogWrote 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/commands/nguyenthienthanh/aura-frog/project)<a href="https://agentmods.dev/commands/nguyenthienthanh/aura-frog/project"><img src="https://agentmods.dev/badge/commands/nguyenthienthanh/aura-frog/project.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 | $0.00000 | $0.00958 |
| Opus 5 | $0.00000 | $0.00479 |
| Sonnet 5 | $0.00000 | $0.00192 |
| Haiku 4.5 | $0.00000 | $0.00096 |
Grade A, and why
project 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 4d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Commands
Unified project management. Handles detection, initialization, configuration, context generation, and environment loading.
/project init
Trigger: First time using Aura Frog in a project, or reconfiguring.
Auto-detects project type (React, Next.js, Laravel, Go, Python, Flutter) and creates the full .claude/ structure: CLAUDE.md, settings.local.json, project-contexts/ with 7 context files (project-config.yaml, conventions.md, rules.md, examples.md, repo-map.md, file-registry.yaml, architecture.md), and session-context.toon (12 pattern detections).
Runs generator scripts (repo-map-gen.sh, file-registry-gen.sh, architecture-gen.sh, context-compress.sh), then Claude enriches output with AI-generated descriptions (~2000 token budget). Merges plugin settings into settings.local.json. Optionally sets up learning system if Supabase credentials exist.
/project detect
Trigger: /project detect -- analyze current directory without initializing.
Scans project root for framework indicators (package.json, composer.json, go.mod, pubspec.yaml, requirements.txt). Reports detected type, tech stack with versions, structure pattern, and recommended configuration (coverage target, TDD enforcement, primary agent). Suggests running /project init to configure.
/project status
Trigger: /project status [project-name] -- show cached detection results.
Displays detected framework, package manager, primary/secondary agents, test framework, templates, and styles without re-scanning. Shows cache age, key files hash, and last scan timestamp. In workspaces, renders a table of all projects with their frameworks, agents, and test setups. Task mentions auto-match to the correct project.
/project list
Trigger: /project list -- list all configured projects.
Shows all Aura Frog-configured projects with their type, path, status, last-used date, team members, and integration status (JIRA, Confluence). Marks the active project. Navigate to a new directory and run /project init to add more.
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.
- 4d ago First seen · 80 lines · 0 tokens per session scan A 5bba8733c089
project is a command published in the GitHub repository nguyenthienthanh/aura-frog (24 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 958 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.
Other commands, from other repositories
review-agentready
AgentReady-specific code review with attribute mapping and score impact analysis.
backlog
The project layer: milestones, epics, and user stories with refusing controllers — spec-seeded, sprint-ready.
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.
resume_handoff
Resume work from handoff document with context analysis and validation.
compose-stack
Compose a sequenced Intelligence Stack Plan for a sovereign person. Analyzes their Genius Profile + Freedom Path + stated priorities + life stage, then sequences which of the 9 layers activate first, second, third. Produces a 90-day sprint plan for building their full intelligence stack. For humans with Genius Profile…
mach12:gh-sub-issues
Detect sub-issues of a GitHub issue using the two-strategy approach (API, then body-parse).