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 hajekim/agentic-design-patterns-skills --skill resource-awaregit clone --depth 1 https://github.com/hajekim/agentic-design-patterns-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/hajekim/agentic-design-patterns-skills/resource-aware)<a href="https://agentmods.dev/skills/hajekim/agentic-design-patterns-skills/resource-aware"><img src="https://agentmods.dev/badge/skills/hajekim/agentic-design-patterns-skills/resource-aware/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/hajekim/agentic-design-patterns-skills/resource-aware"><img src="https://agentmods.dev/badge/skills/hajekim/agentic-design-patterns-skills/resource-aware.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.00408 | $0.03556 |
| Opus 5 | $0.00204 | $0.01778 |
| Sonnet 5 | $0.00082 | $0.00711 |
| Haiku 4.5 | $0.00041 | $0.00356 |
Grade A, and why
resource-aware 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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- resource-aware — 100% identical, 3 lines differ
How it starts
The opening of the file, as written. The whole thing — 377 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resource-Aware Optimization Pattern
Overview
The Resource-Aware Optimization Pattern equips agents with awareness of the computational resources they consume — tokens, API calls, latency, and cost — and strategies to optimize their use. Rather than calling the most capable model for every request or retrieving maximum context every time, resource-aware agents make intelligent trade-offs to achieve goals within budget constraints.
Core Principle: Capability without efficiency is waste — match resource consumption to task requirements.
When This Skill Applies
Activate this pattern when:
- API costs need to stay within budgets (production deployments at scale)
- Latency requirements are strict (real-time user interactions)
- Token limits constrain context window usage
- Rate limits throttle request throughput
- Different sub-tasks have vastly different complexity requirements
- Long-running batch processes must manage resource consumption over time
Rule of thumb: If cost, latency, or quota is a constraint — build resource awareness in from the start, not as an afterthought.
Resource Dimensions
| Resource | Constraint | Optimization Strategy |
|---|---|---|
| Tokens (input) | Context window limit | Summarize, truncate, selective retrieval |
| Tokens (output) | Cost, latency | Precise prompting, structured output |
| API calls | Rate limits, cost | Caching, batching, model selection |
| Latency | User experience | Async, streaming, parallel calls |
| Compute | Server cost | Efficient inference, model cascade |
DEFINE → PLAN → ACTION Workflow
DEFINE
Map resource constraints:
- What are the token budget limits per session/task?
- What is the cost budget? (Per query, per day, per user)
- What are the latency requirements? (P50, P95, P99 targets)
- What rate limits apply? (Requests per minute, tokens per minute)
- Which sub-tasks are latency-sensitive vs. batch-OK?
PLAN
Design resource optimization architecture:
- Define model selection policy: capability vs. cost trade-off by task type
- Design caching strategy: what to cache, TTL, cache invalidation
- Plan context management: how to stay within token limits
- Design batching: group independent requests to amortize overhead
- Build monitoring: track resource usage against budgets in real-time
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.
- 9d ago First seen · 377 lines · 408 tokens per session scan A c5a1bc9ba18f
resource-aware is a skill published in the GitHub repository hajekim/agentic-design-patterns-skills (4 stars, last pushed 5mo ago), licensed MIT. It adds 408 tokens to every session and 3,556 once invoked, about $0.0020 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
impact-audit
Blast radius of a change you have not made yet -- traces a symbol across federated repositories, splits impact per repo, and reports what must ship together.
onboard-repo
Index an unfamiliar codebase into the knowledge graph, then produce a first orientation map -- entry points, most-depended-upon modules, hotspots, test topology.
prompt-optimizer
Analyze raw prompts, identify intent and gaps, match ECC components (skills/commands/agents/hooks), and output a ready-to-paste optimized prompt. Advisory role only — never executes the task itself. TRIGGER when: user says "optimize prompt", "improve my prompt", "how to write a prompt for", "help me prompt", "rewrite…
openclaw-persona-forge
A persona-design guide for OpenClaw agents, including their identity, personality, boundaries, names, and avatar prompts. OpenClaw is the specific agent platform this guide targets.
gemini-api
Google Gemini API patterns for Python and TypeScript. Covers content generation, streaming, tool use (function calling), vision, system instructions, context caching, batch requests, and agent workflows. Use when building applications with the Gemini API or Google Generative AI SDKs.
jira-integration
Use this skill when retrieving Jira tickets, analyzing requirements, updating ticket status, adding comments, or transitioning issues. Provides Jira API patterns via MCP or direct REST calls.