pointer

A command for managing an optional pointer section in the repository's AGENTS.md or CLAUDE.md instructions file. It can show, add, or remove that section with confirmation.

In plain words
What is it for?
Use it to register the command, check pointer status, or update the pointer in the repository root.
Why use it?
It keeps repository guidance consistent while ensuring the pointer is never added automatically.

Command

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 commands/eduardoabreu81/livewiki/pointer
Clone the repo
git clone --depth 1 https://github.com/eduardoabreu81/livewiki
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,951 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 $0.00000 $0.01951
Opus 5 $0.00000 $0.00975
Sonnet 5 $0.00000 $0.00390
Haiku 4.5 $0.00000 $0.00195

Measured 2d ago against content hash 971ca5e40ed3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

pointer 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 2d 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.

livewiki/commands/pointer.md · 122 lines

How it starts

The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Pointer command (livewiki pointer)

This page documents the livewiki pointer subcommand, which manages an opt-in "pointer" block inside an AGENTS.md or CLAUDE.md file at the repository root.

When to use this page

  • Register the livewiki pointer command on a top-level commander program so end users can run it from the CLI.
  • Read or write the livewiki pointer block in AGENTS.md / CLAUDE.md while enforcing the project's "never automatic" opt-in rule.
  • Format the human-readable output that the command prints for status, write, and remove operations.
  • Implement an interactive y/N confirmation prompt that cooperates with commander and respects non-TTY stdin.

How it fits

This module lives in packages/cli/src/commands/pointer.ts. It is one of the commander subcommand registrars in the packages/cli workspace: it wires the pointer command into the top-level program, resolves a target repository root through resolveRepoRoot from ../cli.js, and delegates the actual file mutation to @livewiki/core/pointer (insertPointer, removePointer, readPointerStatus, POINTER_FILES, buildPointerBlock). Human and JSON output is funnelled through the local emit helper from ../output.js. Because the pointer block lives outside the livewiki/ directory, the command enforces a project-wide "Inviolable rule": it must never write automatically — it requires either an explicit flag or interactive confirmation.

Diagram

%% livewiki/diagrams/commands-pointer.mmd

Registering the command

registerPointer is the public surface that the CLI bootstraps call. It owns the lifecycle of the subcommand: defining options, validating input, choosing between status, write, and remove modes, enforcing the opt-in rule, and routing results through emit. Every other symbol in this file exists to support one branch of that lifecycle.

export function registerPointer(program: Command): void

The function takes a commander.Command and returns nothing; its job is to attach a configured pointer subcommand to that program.

Read the full file on GitHub · 122 lines

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. 2d ago First seen · 122 lines · 0 tokens per session scan A 971ca5e40ed3

Subscribe to this mod's changes

pointer is a command published in the GitHub repository eduardoabreu81/livewiki (0 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,951 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.

Related

Other commands, from other repositories

capture-answer

Ingests an expert's answers to an L2 questionnaire in the abapwiki knowledge base: transforms the answers (filled in the interviews/ file or given verbally) into a canonical citable expert-answer (slices/ /inputs/expert-answers/), moves gaps to 'answered' and closes the questions. Use this skill when the owner/expert…

Gixsy95/abap_wiki · 85 tokens

ingest-l1

L1 analysis loop for the abapwiki knowledge base: for each batch it launches the abap-analyzer sub-agent in parallel, then the adversarial judge abap-deepcheck (separate session), applies only the analyses that pass the fail-closed gate, and commits. Resumes exactly after an interruption. Use this skill to document…

Gixsy95/abap_wiki · 86 tokens

research-l2

Executes Phases 1-3 of the L2 process of the abapwiki knowledge base on a slice: launches the abap-functional-researcher sub-agent (gap discovery + multi-source auto-research: wiki -> raw/docs -> MCP abap-fs on the system read-only -> standard knowledge), ingests gaps and evidence, and generates questionnaires for…

Gixsy95/abap_wiki · 111 tokens

slice-init

Creates an L2 slice in the abapwiki knowledge base: a business process on which to build functional documentation. Writes the manifest (curated anchors + mandatory real owner) and derives the membership from the dependency graph (BFS hop<=2). Use this skill to start the L2 process on a custom domain. Does not promote…

Gixsy95/abap_wiki · 83 tokens

ingest-l0

L0 bootstrap of the abapwiki knowledge base: creates stubs for all custom objects from the TADIR. Use this skill to initialize the repo from scratch or to ingest a new TADIR export. Deterministic operations (no LLM sub-agent), idempotent.

Gixsy95/abap_wiki · 59 tokens

lint-audit

Checks the integrity of the abapwiki knowledge base: parseable YAML frontmatter, no broken wikilinks, resolvable [VERIFIED: path:N-M] citations, non-nested confidence tags, drift between wiki and DB, synchronization between canonical agent contracts and the .claude/agents/ copies. Use this skill periodically or after…

Gixsy95/abap_wiki · 74 tokens