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 Incept5/eve-skillpacks --skill eve-job-lifecyclegit clone --depth 1 https://github.com/Incept5/eve-skillpacksWrote 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/incept5/eve-skillpacks/eve-job-lifecycle)<a href="https://agentmods.dev/skills/incept5/eve-skillpacks/eve-job-lifecycle"><img src="https://agentmods.dev/badge/skills/incept5/eve-skillpacks/eve-job-lifecycle/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/incept5/eve-skillpacks/eve-job-lifecycle"><img src="https://agentmods.dev/badge/skills/incept5/eve-skillpacks/eve-job-lifecycle.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.00034 | $0.00298 |
| Opus 5.5 | $0.00014 | $0.00119 |
| Sonnet 5.5 | $0.00007 | $0.00060 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
eve-job-lifecycle 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 2mo 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
Eve Job Lifecycle
Use jobs as the unit of work and keep phases explicit.
Phases
- idea -> backlog -> ready -> active -> review -> done or cancelled
- Jobs default to
readyand can be scheduled immediately.
Create jobs
eve job create --description "..."- Add details with
--project,--priority,--phase,--labels,--review. - Create sub-jobs with
eve job create --parent <job-id> --description "...".
Update and complete
eve job update <id> --phase <phase>eve job submit <id> --summary "..."eve job approve <id>oreve job reject <id> --reason "..."eve job close <id> --reason "..."eve job cancel <id> --reason "..."
Dependencies
eve job dep add <job> <blocking-job>- Use dependencies only for true blockers.
- Inspect with
eve job dep list <id>.
Agent control signals
- Emit a fenced
json-resultblock witheve.statusaswaiting,success, orfailed. - Return
waitingonly after dependencies exist.
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.
- 2mo ago First seen · 38 lines · 34 tokens per session scan A 25248e6ff5b5
eve-job-lifecycle is a skill published in the GitHub repository Incept5/eve-skillpacks (0 stars, last pushed 4mo ago), licensed MIT. It adds 34 tokens to every session and 298 once invoked, about $0.0001 per session on Opus 5.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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
dev-console-context
Use when the user mentions Developer Console, projects, workspaces, credentials, or orgs — or uses phrases like "show my projects", "list workspaces", "get credentials", "switch project", "which org", "my org", "console", "navigate", "explore", "what projects do I have", "show credentials", "what workspace". Also use…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
remove
Remove a deployed framework or addon from the current workspace.