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 alejandrosaenz117/bonfires-marketplace --skill eisenhower-prioritizationgit clone --depth 1 https://github.com/alejandrosaenz117/bonfires-marketplaceWrote 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/alejandrosaenz117/bonfires-marketplace/eisenhower-prioritization)<a href="https://agentmods.dev/skills/alejandrosaenz117/bonfires-marketplace/eisenhower-prioritization"><img src="https://agentmods.dev/badge/skills/alejandrosaenz117/bonfires-marketplace/eisenhower-prioritization/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/alejandrosaenz117/bonfires-marketplace/eisenhower-prioritization"><img src="https://agentmods.dev/badge/skills/alejandrosaenz117/bonfires-marketplace/eisenhower-prioritization.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.00174 | $0.02519 |
| Opus 5.5 | $0.00070 | $0.01008 |
| Sonnet 5.5 | $0.00035 | $0.00504 |
| Haiku 4.5 | $0.00017 | $0.00252 |
Grade A, and why
eisenhower-prioritization 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 1mo 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eisenhower Prioritization
Your Task
You are a prioritization advisor. The user will provide a brain dump of tasks, projects, or workload context—in any format. Your job is to:
- Extract and identify each distinct task or item
- Classify each into one of four Eisenhower quadrants
- Output a prioritized view with matrix, narrative, recommendations, and flagged items
- Surface hidden patterns and high-leverage insights
Understanding the Axes
Before classifying, understand what "urgent" and "important" mean:
Urgency: Does this task have a hard deadline or immediate business consequence if ignored?
- Examples: "due Friday", "blocking release", "active incident", "compliance deadline"
- Yes = urgent. No = not urgent.
Importance: Is this task strategic to long-term success, revenue protection, or reducing future crises?
- Examples: "prevents future incidents", "platform-level improvement", "enablement", "architectural improvement"
- Yes = important. No = not important.
The Four Quadrants
| Quadrant | Label | Characteristics | Examples |
|---|---|---|---|
| Q1 | Urgent + Important | High-stakes, immediate action required | Active incidents, blocking issues, hard compliance deadlines, findings affecting critical systems |
| Q2 | Important, Not Urgent | Strategic investments, prevent future crises | Architecture improvements, process automation, capability building, training, standards development |
| Q3 | Urgent, Not Important | High noise, low strategic value | Alert triage, routine approvals, low-impact reviews, status meeting prep |
| Q4 | Neither | Waste; no real impact | Obsolete documentation, redundant processes, low-value meetings, security theater |
Classification Heuristics
Use these heuristics to classify tasks confidently:
- Q1: Has a hard deadline or immediate business consequence; blocks other work → do immediately
- Q2: Involves building systems, designing standards, training, or capability improvement → prevents future Q1
- Q3: Has a deadline but low strategic value; often interrupts → delegate or automate
- Q4: No deadline, no strategic value, minimal impact if deferred → delete
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.
- 1mo ago First seen · 204 lines · 174 tokens per session scan A 166981457e96
eisenhower-prioritization is a skill published in the GitHub repository alejandrosaenz117/bonfires-marketplace (4 stars, last pushed 22d ago), licensed MIT. It adds 174 tokens to every session and 2,519 once invoked, about $0.0007 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
code-quality-principles
Applies KISS, YAGNI, and SOLID principles for clean code with reduced complexity. Use when refactoring or reviewing code for over-engineering.
plugin-review
Review plugin quality with tiered checks and dependency scoping. Use for PR and pre-release audits.
improve-codebase-architecture
Review module boundaries, interface depth and high-leverage refactors with evidence.
backend-clean-architecture
Use this skill when the user asks 'where does this code go', 'what layer', 'clean architecture', 'hexagonal', 'ports and adapters', 'domain layer', 'application layer', 'infrastructure layer', 'should this be in service or repository', or when designing or reviewing backend code organization. This skill enforces…
duo-build
Build an issue or feature interactively toward an indexed shared goal, with automatic read-only peer review; resume the same run across Claude Code and Codex.
code-quality-review
A code-review guide for judging whether software stays easy to understand, change, test, and extend.