memory-ticketing

memory-ticketing is a skill for Claude Code, Codex from agentlas-ai/Agentlas-OS. It costs 37 tokens per session (169 once invoked), scanned A, original, Apache-2.0.

A set of rules and files for recording project memory events and routing them through review. It covers memory tickets, references, ownership, redaction, and deduplication.

In plain words
What is it for?
Use it when adding or maintaining memory maps, memory tickets, vault references, or memory-curation workflows in an agent repository.
Why use it?
It helps teams preserve useful project context without storing secrets, credentials, raw logs, or full conversation transcripts.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

About the project

Agentlas OS is a local-first system for creating, storing, borrowing, and running specialist AI agents and temporary agent teams through supported hosts and models. It serves people who want reusable agents that remain available across computers and model workspaces, and the catalogue contains its skills, commands, hooks, agents, instructions, plugin, and rule.

agentlas-ai/Agentlas-OS · 1,101 stars · on GitHub · agentlas.cloud

Install

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.

agentmods
npx agentmods add skills/agentlas-ai/agentlas-os/memory-ticketing
Any agent
npx skills add agentlas-ai/Agentlas-OS --skill memory-ticketing
Clone the repo
git clone --depth 1 https://github.com/agentlas-ai/Agentlas-OS

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for memory-ticketing

README.md
[![agentmods](https://agentmods.dev/badge/skills/agentlas-ai/agentlas-os/memory-ticketing.svg)](https://agentmods.dev/skills/agentlas-ai/agentlas-os/memory-ticketing)
Your own site
<a href="https://agentmods.dev/skills/agentlas-ai/agentlas-os/memory-ticketing"><img src="https://agentmods.dev/badge/skills/agentlas-ai/agentlas-os/memory-ticketing.svg" alt="Measured on agentmods" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 169 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00037 $0.00169
Opus 5 $0.00018 $0.00084
Sonnet 5 $0.00007 $0.00034
Haiku 4.5 $0.00004 $0.00017

Measured 6d ago against content hash 7ea4fe261905, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

memory-ticketing 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 6d 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.

.agents/skills/memory-ticketing/SKILL.md · 26 lines

What it actually says

Memory Ticketing

Required Files

  • .agentlas/memory-map.json
  • .agentlas/memory-tickets.jsonl
  • .agentlas/vault-references.json

Flow

  1. Workers emit ## Memory Events.
  2. Runtime or orchestrator wraps events into tickets.
  3. Memory Curator validates, redacts, deduplicates, and routes.
  4. PM Soul owns project memory and open loops.
  5. Policy Gate approves shared team-memory promotion.

Never Store

Secrets, credentials, private keys, tokens, service-account JSON, raw logs, or full transcripts.

Changes

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.

  1. 6d ago First seen · 26 lines · 37 tokens per session scan A 7ea4fe261905

Subscribe to this mod's changes

memory-ticketing is a skill published in the GitHub repository agentlas-ai/Agentlas-OS (1,101 stars, last pushed 3d ago), licensed Apache-2.0. It adds 37 tokens to every session and 169 once invoked, about $0.0002 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.