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 Maless88/Roadboard --skill archive-artifactgit clone --depth 1 https://github.com/Maless88/RoadboardWrote 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/maless88/roadboard/archive-artifact)<a href="https://agentmods.dev/skills/maless88/roadboard/archive-artifact"><img src="https://agentmods.dev/badge/skills/maless88/roadboard/archive-artifact.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.1 | $0.00056 | $0.00481 |
| Opus 5 | $0.00028 | $0.00241 |
| Sonnet 5 | $0.00011 | $0.00096 |
| Haiku 4.5 | $0.00006 | $0.00048 |
Grade A, and why
archive-artifact 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 8d 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
Archive an artifact into RoadBoard
When you produce a deliverable that should outlive the conversation, archive it in RoadBoard via its MCP tools (single source of truth) — never in side files.
When to archive
- A completed analysis, audit report, design note, or research summary.
- A handoff to another agent or to the user.
- A reference to a generated asset (image/diagram): store its path/URL + a description. Skip trivial chat replies and intermediate scratch.
How
Use create_memory_entry with this envelope:
- title:
[<your-name>] <concise subject>(e.g.[Argo] Security audit — auth module). - type: pick from the allowed set by nature of the artifact:
issue— findings/problems (e.g. a security audit's findings)architecture— structural/design analysislearning— research summary, lessons, evaluationdecision— a recorded choice (prefercreate_decisionif it's a real decision)handoff— next-steps handoff (prefercreate_handoff)operational_note— anything else worth keeping
- body (markdown): the artifact itself. For findings, list each with severity
(Critical/High/Medium/Low) and
file:line. For a generated asset, include its path/URL and a one-line description. End with a footer line:— archived by <your-name>, <project>. - Always pass the correct projectId (the project in your context).
Rules
- Everything goes in via MCP; do not write artifacts to local files as the system of record.
- Don't claim you archived something unless
create_memory_entry(orcreate_decision/create_handoff) actually returned success. - One entry per artifact; keep titles searchable (they surface via
search_memory).
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.
- 8d ago First seen · 38 lines · 56 tokens per session scan A b038a83a2583
archive-artifact is a skill published in the GitHub repository Maless88/Roadboard (2 stars, last pushed 24d ago), licensed MIT. It adds 56 tokens to every session and 481 once invoked, about $0.0003 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
lc-curate-context
Decide which files a task actually needs, record that as a reusable llm-context rule, verify it against the codebase - including the files your selection references but leaves out - and pack it for your own context, a chat, or a sub-agent you dispatch. Load when choosing what code to put in front of a model, packing…
cortex-automate
Set up automation — prospective memory triggers, neuro-symbolic rules, and CLAUDE.md sync. Use when the user says 'remind me when', 'trigger when', 'create a rule', 'auto-remember', 'sync to CLAUDE.md', 'push insights', 'set up trigger', 'when I open this file', 'when this keyword appears', or when you want to…
cortex-remember-global
Store a global memory that is visible across all projects. Use when the user shares architecture rules, coding conventions, infrastructure facts, security policies, team agreements, or any knowledge that applies beyond a single project. Triggers on 'remember this everywhere', 'this applies to all projects', 'global…
cortex-consolidate
Run memory maintenance — decay old memories, compress stale content, consolidate episodic memories into semantic knowledge, and run sleep-like replay. Use when the user says 'clean up memories', 'consolidate', 'run maintenance', 'compress old memories', 'memory cleanup', or periodically to keep the memory system…
cortex-explore-memory
Explore the memory system's state, find gaps in knowledge, assess coverage, and get diagnostic information. Use when the user asks 'what does my memory look like', 'show me memory stats', 'what am I missing', 'how good is my knowledge', 'memory health', 'show coverage', 'find gaps', 'what topics are weak', or when you…
cortex-navigate-knowledge
Navigate the knowledge graph — trace entity relationships, explore causal chains, drill into memory clusters, and traverse co-access paths. Use when the user asks 'how are these related', 'what connects X to Y', 'show me the knowledge graph', 'trace the relationship', 'what caused X', 'drill down into', 'explore…