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 PugzUI/axom --skill axom-analyzegit clone --depth 1 https://github.com/PugzUI/axomWrote 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/pugzui/axom/axom-analyze)<a href="https://agentmods.dev/skills/pugzui/axom/axom-analyze"><img src="https://agentmods.dev/badge/skills/pugzui/axom/axom-analyze/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/pugzui/axom/axom-analyze"><img src="https://agentmods.dev/badge/skills/pugzui/axom/axom-analyze.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.00000 | $0.00795 |
| Opus 5.5 | $0.00000 | $0.00318 |
| Sonnet 5.5 | $0.00000 | $0.00159 |
| Haiku 4.5 | $0.00000 | $0.00080 |
Grade A, and why
axom-analyze 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Axom Analyze Skill
Deep analysis. Actionable output. Memory integration. Analysis without storage is wasted. Chain findings to memory. Use reflex for heuristics.
Core Mandate
Analysis without storage is wasted insight. Use chain
to write findings to memory. The next agent (or you, later)
will search and find what you learned. Make analysis persist.
Analysis Types
| Type | Purpose | Depth | When |
|---|---|---|---|
debug |
Isolate issues | high–max | Errors, symptoms, flaky behavior |
review |
Code quality, patterns | medium–high | Assessment, style, structure |
audit |
Security, compliance | max | Vulnerabilities, policy violations |
refactor |
Improve structure | medium | Performance, readability |
test |
Test coverage, gaps | medium | Missing tests, brittle tests |
Parameters
| Param | Values | Use |
|---|---|---|
type |
debug, review, audit, refactor, test | Required |
target |
File path or code block | Required |
focus |
e.g. "security", "performance" | Narrow the analysis |
depth |
minimal, low, medium, high, max | Deeper = more thorough |
output_format |
summary, detailed, actionable | actionable = concrete steps |
Chained Remediation: Store What You Find
Pattern: Analyze → Store in memory
{
"type": "debug",
"target": "broken_function.py",
"depth": "high",
"focus": "TypeError on line 42",
"chain": [
{
"condition": "${_result.issues_found} == true",
"tool": "axom_mcp_memory",
"args": {
"action": "write",
"name": "bugfix_analysis_20260222",
"content": "TASK: Debug TypeError\nAPPROACH: ${_result.summary}\nOUTCOME: Pending fix\nGOTCHAS: ${_result.details}",
"importance": "high",
"memory_type": "short_term"
}
}
]
}
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 · 102 lines · 0 tokens per session scan A 1d90bbdd04cb
axom-analyze is a skill published in the GitHub repository PugzUI/axom (0 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 795 tokens. 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
sync-bridge
Reviews and guides Chromium Sync Model API (DataTypeSyncBridge) implementations, including DataTypeStore persistence and forwards/backwards compatibility for sync specifics. Use when implementing or reviewing a DataTypeSyncBridge subclass, DataTypeStore usage, sync metadata persistence, conflict resolution, or…
sync-model-processor
Reviews changes to Chromium Sync model internals in components/sync/model/, including ClientTagBasedDataTypeProcessor, ClientTagBasedRemoteUpdateHandler, ProcessorEntity, ProcessorEntityMetadata, and ProcessorEntityTracker. Use when modifying or reviewing processor state transitions, entity metadata tracking, conflict…
adversarial-reviewer
Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart, or to check your own change before submitting it. Do not use for ordinary review, style feedback, or general…
gsd-ns-review
Invoke this Pi skill with /skill:gsd-ns-review.
gitnexus
A code-graph analysis add-on for examining an existing codebase, including symbols, call paths, execution flows, and effects across repositories. It can query GitNexus through its command-line or MCP interfaces.
issue
Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…