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/ambient-code/platform/jira.loggit clone --depth 1 https://github.com/ambient-code/platformWhat 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.00025 | $0.02099 |
| Opus 5 | $0.00013 | $0.01050 |
| Sonnet 5 | $0.00005 | $0.00420 |
| Haiku 4.5 | $0.00003 | $0.00210 |
Grade A, and why
jira.log 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 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 — 293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Goal
Create a new Jira Story in the RHOAIENG project with the correct Team and Component pre-filled for the Ambient team.
Execution Steps
1. Parse User Input
Extract the following from $ARGUMENTS:
- Summary (required): The title/summary of the issue
- Description (optional): Detailed description of the work
- Issue Type (optional): Defaults to
Story, but can beBugorTask. Tasks are tech debt related and not user facing. Normalize case before use (e.g. "bug" → "Bug", "TASK" → "Task") and validate against this allowlist; reject unrecognized values with a prompt to the user. - Priority (optional): Defaults to
Normal
If the user provides a simple sentence, use it as the summary. If they provide multiple lines, use the first line as summary and the rest as description.
2. Gather Cold-Start Context
IMPORTANT: To make this Jira actionable by an agent, gather the following context. Ask the user for any missing critical info:
Required for Stories:
- What is the user-facing goal? (As a [user], I want [X], so that [Y])
- What are the acceptance criteria? (How do we know it's done)
- Which repo/codebase? (e.g.,
vTeam,ambient-cli)
Required for Bugs:
- Steps to reproduce
- Expected vs actual behaviour
- Environment/browser info if relevant
Helpful for all types:
- Relevant file paths or components (e.g.,
components/frontend/src/...) - Related issues/PRs/design docs
- Screenshots or mockups (as links)
- Constraints or out-of-scope items
- Testing requirements
3. Build Structured Description
Format the description using this agent-friendly template:
## Overview
[One paragraph summary of what needs to be done and why]
## User Story (for Stories)
As a [type of user], I want [goal], so that [benefit].
## Acceptance Criteria
- [ ] [Criterion 1]
- [ ] [Criterion 2]
- [ ] [Criterion 3]
## Technical Context
**Repo**: [repo name or URL]
**Relevant Paths**:
- `path/to/relevant/file.ts`
- `path/to/another/area/`
## Related Links
- Design: [link if any]
- Related Issues: [RHOAIENG-XXXX]
- PR: [link if any]
## Constraints
- [What NOT to do]
- [Boundaries to respect]
## Testing Requirements
- [ ] Unit tests for [X]
- [ ] E2E test for [Y]
## Bug Details (for Bugs only)
**Steps to Reproduce**:
1. Step 1
2. Step 2
**Expected**: [what should happen]
**Actual**: [what actually happens]
**Environment**: [browser/OS if relevant]
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.
- yesterday First seen · 293 lines · 25 tokens per session scan A 97a4a58acab1
jira.log is a command published in the GitHub repository ambient-code/platform (129 stars, last pushed 2d ago), licensed MIT. It adds 25 tokens to every session and 2,099 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 commands, from other repositories
MIGRATE_DESIGN
Design doc for the migration tool PR. Author: Sol ([email protected]). Co-authored-by: wakesync.
proposal
Create a structured feature proposal in docs/11-proposals/.
plan
Create a structured task-by-task implementation plan for a feature and write it to docs/superpowers/plans/.
diff-script
Compare an MDL script against the project's current state.
toh-help
Display all Toh Framework commands and quick usage guide.
doctor
Run procedural readiness checks for goal-flight.