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/anomalyarmor/agents/tagsnpx skills add anomalyarmor/agents --skill tagsgit clone --depth 1 https://github.com/anomalyarmor/agentsWhat 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.00039 | $0.00936 |
| Opus 5 | $0.00019 | $0.00468 |
| Sonnet 5 | $0.00008 | $0.00187 |
| Haiku 4.5 | $0.00004 | $0.00094 |
Grade A, and why
armor-tags 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.
How it starts
The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Classification with Tags
Organize and classify database objects with tags for governance, compliance, and business categorization.
Prerequisites
- AnomalyArmor API key configured (
~/.armor/config.yamlorARMOR_API_KEYenv var) - Python SDK installed (
pip install anomalyarmor)
When to Use
- "Tag this table as PII"
- "Apply financial reporting tag"
- "List all tags for this asset"
- "Mark these columns as sensitive"
- "Classify this data as confidential"
- "Add governance labels"
Concepts
Tag Categories
- business: Business domain tags (e.g., "finance", "marketing", "sales")
- technical: Technical classification (e.g., "fact_table", "dimension", "staging")
- governance: Compliance and security (e.g., "pii", "confidential", "gdpr")
Tag Scope
Tags can be applied to:
- Tables: Full table classification
- Columns: Column-level classification (for PII, sensitive data)
Steps
Creating a Tag
- Identify the asset and object (table or column) to tag
- Choose the tag name and category
- Call
client.tags.create()with the object path
Applying Multiple Tags
- Prepare list of tag names to apply
- Prepare list of object paths
- Call
client.tags.apply()for batch operations
Bulk Tagging Across Assets
- Create tag name
- List asset IDs to tag
- Call
client.tags.bulk_apply()
Example Usage
List Existing Tags
from anomalyarmor import Client
client = Client()
# List all tags for an asset
tags = client.tags.list(asset="postgresql.analytics")
for tag in tags:
print(f" {tag.name} ({tag.category}): {tag.object_path}")
# Filter by category
governance_tags = client.tags.list(
asset="postgresql.analytics",
category="governance"
)
Tag a Table as PII
tag = client.tags.create(
asset="postgresql.analytics",
name="pii_data",
object_path="public.customers",
object_type="table",
category="governance",
description="Contains personally identifiable information"
)
print(f"Created tag: {tag.id}")
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.
- 2d ago First seen · 154 lines · 39 tokens per session scan A c10018f84aa9
armor-tags is a skill published in the GitHub repository anomalyarmor/agents (1 stars, last pushed 3mo ago), licensed MIT. It adds 39 tokens to every session and 936 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.