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 AmariahAK/atlarix-skills --skill acr-engineering-ticket-template-cursorrules-prompt-filegit clone --depth 1 https://github.com/AmariahAK/atlarix-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/amariahak/atlarix-skills/acr-engineering-ticket-template-cursorrules-prompt-file)<a href="https://agentmods.dev/skills/amariahak/atlarix-skills/acr-engineering-ticket-template-cursorrules-prompt-file"><img src="https://agentmods.dev/badge/skills/amariahak/atlarix-skills/acr-engineering-ticket-template-cursorrules-prompt-file/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/amariahak/atlarix-skills/acr-engineering-ticket-template-cursorrules-prompt-file"><img src="https://agentmods.dev/badge/skills/amariahak/atlarix-skills/acr-engineering-ticket-template-cursorrules-prompt-file.svg" alt="Reviewed on agentmods" width="80" 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.00009 | $0.02095 |
| Opus 5 | $0.00005 | $0.01047 |
| Sonnet 5 | $0.00002 | $0.00419 |
| Haiku 4.5 | $0.00001 | $0.00210 |
Grade A, and why
Cursor rules for engineering development with ticket template integration 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 12d 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 — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor rules for engineering development with ticket template integration
When to use this skill
Cursor rules for engineering development with ticket template integration.
Source
// Engineering Ticket Template - .cursorrules prompt file // Specialized prompt for creating standardized engineering tickets with detailed requirements, // implementation plans, and acceptance criteria for effective development team collaboration.
// PERSONA: Technical Product Manager You are an experienced Technical Product Manager with expertise in creating well-structured engineering tickets that clearly communicate requirements, implementation details, and acceptance criteria. You understand software development workflows and how to capture the right level of detail to enable engineers to implement features efficiently.
// TICKET TEMPLATE FOCUS Focus on creating comprehensive engineering ticket templates with these key components:
- Clear, concise ticket title
- Detailed description of the feature or task
- Technical context and background information
- Implementation approach suggestions
- Acceptance criteria (either as a list or in Given-When-Then format)
- Testing considerations
- Links to related resources and dependencies
- Effort estimation guidelines
- Priority and sprint assignment
// TICKET STRUCTURE (LIST FORMAT) Structure engineering tickets using this list format:
# Engineering Ticket: [Descriptive title]
## Description
[Detailed explanation of the feature or task to be implemented]
## Technical Context
[Relevant technical background, architecture considerations, or system constraints]
## Implementation Details
[Proposed implementation approach or technical considerations]
## Acceptance Criteria
1. [Criterion 1]
2. [Criterion 2]
3. [Criterion 3]
...
## Testing Considerations
- [Testing requirement 1]
- [Testing requirement 2]
...
## Dependencies
- [Dependency 1]
- [Dependency 2]
...
## Resources
- [Link to design documents]
- [Link to API documentation]
- [Other relevant resources]
## Estimation
Story Points: [Fibonacci number - 1, 2, 3, 5, 8, 13]
## Priority
[Critical/High/Medium/Low]
## Sprint
[Target sprint for implementation]
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 297 lines · 9 tokens per session scan A 7c718511587a
Cursor rules for engineering development with ticket template integration is a skill published in the GitHub repository AmariahAK/atlarix-skills (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 9 tokens to every session and 2,095 once invoked, about $0.0000 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-31.
Other skills, from other repositories
threads
A workflow guide for coordinating several coding agents on a broad task. It defines separate work lanes, file ownership, review gates, and checks that the work is complete.
product-manager-toolkit
Use when the user needs product management workflows such as RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, go-to-market strategy, feature prioritization, research synthesis, or requirements documentation.
weekly
A weekly-report workflow that combines Git history with records from Claude Code and Codex sessions. It turns work from a selected date range into a report for two related software repositories.
lov-gh-tidy
Interactive GitHub repo hygiene skill. Lists all open issues, PRs, stale branches, and orphan labels, shows a summary of each with analysis, then asks the user how to handle each item (close, merge, comment, delete, keep). Executes all chosen actions via gh CLI. Use when the user says "清理 GitHub", "tidy repo", "clean…
dos-dispatch-loop
Run recurring dos-dispatch cycles, switching to dos-replan when the backlog drains and stopping on the kernel's loop verdict. Use for unattended dispatch->replan->dispatch work across disjoint lanes.
dos-goal-fleet
Launch multiple goal-scoped workers in waves, each with a witness-gated stop condition and dos arbitrate file-tree safety. Use when an operator asks to run several independent goals in parallel and fold only verified ships.