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 skills/fisker086/aiops/self_improving_agentnpx skills add fisker086/AIOps --skill self_improving_agentgit clone --depth 1 https://github.com/fisker086/AIOpsWrote 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/fisker086/aiops/self_improving_agent)<a href="https://agentmods.dev/skills/fisker086/aiops/self_improving_agent"><img src="https://agentmods.dev/badge/skills/fisker086/aiops/self_improving_agent.svg" alt="Measured on agentmods" 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 | $0.00018 | $0.00607 |
| Opus 5 | $0.00009 | $0.00303 |
| Sonnet 5 | $0.00004 | $0.00121 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
self-improving-agent 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 4d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Self-Improving Agent
This skill enables continuous improvement by tracking errors, lessons learned, and user corrections. Uses persistent database storage.
When to Use
Use this skill proactively in these scenarios:
- Command or operation fails unexpectedly - A tool execution fails, command returns error
- User corrects you - User says "no, that's wrong", "not what I meant", or provides corrections
- Repeated failures - Same type of error occurs multiple times
- Unknown uncertainty - Not sure if approach is correct, want to verify before proceeding
How It Works
Using the Tool
Use builtin_learning tool with the following operations:
1. Record a Learning (add)
Record what you learned from an error or correction:
operation: "add"
error_type: "shell_command_permission_denied"
context: "Tried to run 'apt-get install' without sudo"
root_cause: "User not in sudoers file"
fix: "Use 'sudo' prefix or check if user has permission"
lesson: "Always check if elevated permissions are needed before system commands"
Parameters:
operation: "add" or "create"error_type: Short identifier (e.g., "shell_permission", "wrong_editor")context: What were you trying to do?root_cause: Why did it fail?fix: What did you do differently?lesson: What did you learn? (general principle)user_id: User ID (optional, omit for global learning)
2. List Learnings (list)
Get all learnings for a user (or global if no user_id):
operation: "list"
user_id: "123"
3. Get Specific Learning (get)
Retrieve a specific learning by error_type:
operation: "get"
error_type: "shell_command_permission_denied"
Key Principles
- Don't repeat mistakes - Apply learnings to avoid same class of errors
- Be specific - Log concrete details, not vague notes
- Extract patterns - Look for recurring themes
- Acknowledge uncertainty - It's okay to ask for verification when unsure
- Learn from users - Their corrections are valuable feedback
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.
- 4d ago First seen · 82 lines · 18 tokens per session scan A d3237a62ff95
self-improving-agent is a skill published in the GitHub repository fisker086/AIOps (22 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 18 tokens to every session and 607 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 skills, from other repositories
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
ljg-learn
Deep concept anatomist that deconstructs any concept through 8 exploration dimensions (history, dialectics, phenomenology, linguistics, formalization, existentialism, aesthetics, meta-philosophy) and compresses insights into an epiphany. Use when user asks to explain, dissect, or deeply understand a concept, term, or…
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.
code-documenter
Use when adding docstrings, creating API documentation, or building documentation sites. Invoke for OpenAPI/Swagger specs, JSDoc, doc portals, tutorials, user guides.
deck-course-module
暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.
grid-ctf-ops
Operational knowledge for the gridctf scenario including strategy playbook, lessons learned, and resource references. Use when generating, evaluating, coaching, or debugging gridctf strategies.