Install the "artifact-metadata" agent skill from https://github.com/jmagly/aiwg/tree/main/agentic/code/plugins/utils/skills/artifact-metadata into .claude/skills/artifact-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "artifact-metadata", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add jmagly/aiwg --skill artifact-metadata -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "artifact-metadata" agent skill from https://github.com/jmagly/aiwg/tree/main/agentic/code/plugins/utils/skills/artifact-metadata into .agents/skills/artifact-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "artifact-metadata", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add jmagly/aiwg --skill artifact-metadata -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "artifact-metadata" agent skill from https://github.com/jmagly/aiwg/tree/main/agentic/code/plugins/utils/skills/artifact-metadata into .cursor/skills/artifact-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "artifact-metadata", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add jmagly/aiwg --skill artifact-metadata -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "artifact-metadata" agent skill from https://github.com/jmagly/aiwg/tree/main/agentic/code/plugins/utils/skills/artifact-metadata into .gemini/skills/artifact-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "artifact-metadata", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
GitHub CLI
$ gh skill install jmagly/aiwg artifact-metadata
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add jmagly/aiwg --skill artifact-metadata -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "artifact-metadata" agent skill from https://github.com/jmagly/aiwg/tree/main/agentic/code/plugins/utils/skills/artifact-metadata into .github/skills/artifact-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "artifact-metadata", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add jmagly/aiwg --skill artifact-metadata -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "artifact-metadata" agent skill from https://github.com/jmagly/aiwg/tree/main/agentic/code/plugins/utils/skills/artifact-metadata into .opencode/skills/artifact-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "artifact-metadata", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
artifact-metadata
GitHub stars
220
Token cost
~1.9k tokens
SKILL.md length
316 words
Files
2 (incl. scripts)
Skills in repo
11
Repo updated
First seen
Licence
MIT
At a glance
Manage artifact metadata, versioning, ownership, and review history across the SDLC lifecycle
Works in 4 steps: Locates or creates metadata → Updates metadata fields → Tracks history → …
SKILL.md covers Triggers, Purpose, Behavior and Metadata Schema, plus 8 more sections
Runs Python scripts from its folder; calls python; reaches json-schema.org
What it does
Artifact Metadata is an agent skill from jmagly/aiwg. Manage artifact metadata, versioning, ownership, and review history across the SDLC lifecycle
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/artifact_metadata.py`).
The repository describes itself as: Cognitive architecture for AI-augmented software development. Specialized agents, structured workflows, and multi-platform deployment. Claude Code · Codex · Copilot · Cursor ·… The licence is MIT.
Example prompts
“/artifact-metadata”
Requirements
Python 3
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
1Locates or creates metadata
2Updates metadata fields
3Tracks history
4Validates relationships
What it can do on your machine
Read from SKILL.md and the folder at commit dda238f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
json-schema.org
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Artifact Metadata loads about 1.9k tokens when it runs. Until then it costs about 28 tokens; SKILL.md has 316 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~28
When it runs· the whole SKILL.md, loaded when a task matches
~1.9k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
Download SKILL.mdSave it as .claude/skills/artifact-metadata/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
artifact-metadata
description
Manage artifact metadata, versioning, ownership, and review history across the SDLC lifecycle
namespace
aiwg
platforms
all
artifact-metadata
Manage artifact metadata, versioning, ownership, and history tracking.
Triggers
Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):
This skill provides consistent metadata management for all SDLC and marketing artifacts. It tracks ownership, versioning, review history, and status across the artifact lifecycle.
Behavior
When triggered, this skill:
Locates or creates metadata:
Check for existing metadata.json alongside artifact
User: "Version the SAD to 1.0.0 with summary 'Initial baseline'"
Skill updates:
- version: "1.0.0"
- status: "baselined"
- baselined: "2025-12-08T16:45:00Z"
- history: [adds entry with version, date, summary]
Record Review
User: "Record security-architect review as approved"
Skill updates:
- reviews: [adds review record]
- reviewers: [adds "security-architect" if not present]
- modified: [updates timestamp]
Query Ownership
User: "Who owns the test plan?"
Skill responds:
"Test Plan (TP-001) is owned by test-architect.
Status: review
Version: 0.3.0
Last modified: 2025-12-07
Reviewers: security-auditor, requirements-analyst"
Status Lifecycle
draft → review → approved → baselined
↑ ↓
└── rejected (returns to draft)
baselined → deprecated (end of life)
Status Transitions
From
To
Triggered By
draft
review
Submit for review
review
approved
All reviewers approve
review
draft
Any reviewer rejects
approved
baselined
Formal baseline action
baselined
deprecated
Superseded or retired
Version Conventions
0.x.x: Draft versions (not baselined)
1.0.0: First baseline
x.y.0: Minor changes (compatible)
x.0.0: Major changes (may break traceability)
Auto-Version Rules
Change Type
Version Bump
Typo fix
patch (0.0.x)
Section update
minor (0.x.0)
Structure change
major (x.0.0)
Initial baseline
1.0.0
Artifact Type Conventions
Type
ID Prefix
Location
requirements
UC-, REQ-, NFR-
.aiwg/requirements/
architecture
SAD-, ADR-, API-
.aiwg/architecture/
test
TP-, TC-, TS-
.aiwg/testing/
security
TM-, SEC-
.aiwg/security/
deployment
DP-, RN-
.aiwg/deployment/
marketing
CB-, CA-
.aiwg/marketing/
report
RPT-
.aiwg/reports/
CLI Usage
bash
# Create metadata for artifact
python artifact_metadata.py --create --artifact ".aiwg/architecture/sad.md" --type architecture
# Update version
python artifact_metadata.py --version "1.0.0" --artifact ".aiwg/architecture/sad.md" --summary "Initial baseline"
# Record review
python artifact_metadata.py --review --artifact ".aiwg/architecture/sad.md" \
--reviewer "security-architect" --outcome "approved" --comments "LGTM"
# Query metadata
python artifact_metadata.py --query --artifact ".aiwg/architecture/sad.md"
# List all artifacts by status
python artifact_metadata.py --list --status "review"
# Validate all metadata
python artifact_metadata.py --validate-all
Integration
This skill integrates with:
artifact-orchestration: Sets initial metadata when creating artifacts
gate-evaluation: Checks artifact status for gate criteria
traceability-check: Uses traceability links in metadata
template-engine: Copies metadata template on instantiation
Artifact Metadata next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Extracts and analyzes browser history, cookies, cache, downloads, and bookmarks from Chrome, Firefox, and Edge using sqlite3, DB Browser for SQLite, Hindsight, and NirSoft tools…
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui).
Work safely with endpoint versions — preview a draft in the playground, roll back to an older version, update settings on one version without bumping query history, deactivate a specific version.
Scan source code for banned APIs/forbidden functions per project banlist; report violations with paths, line numbers, and recommended replacements
220 GitHub stars~2.2k tokensUpdated today
Auto-check passed
Questions about Artifact Metadata
What does Artifact Metadata do?
Manage artifact metadata, versioning, ownership, and review history across the SDLC lifecycle. Artifact Metadata is an agent skill from jmagly/aiwg.
How do I install Artifact Metadata in Claude Code?
Run `npx skills add jmagly/aiwg --skill artifact-metadata -a claude-code`. Or copy the skill folder (agentic/code/plugins/utils/skills/artifact-metadata in jmagly/aiwg) into .claude/skills/artifact-metadata in your project. Claude Code loads it when a task matches its description.
How do I install Artifact Metadata in Codex?
Run `npx skills add jmagly/aiwg --skill artifact-metadata -a codex`. Or copy the skill folder (agentic/code/plugins/utils/skills/artifact-metadata in jmagly/aiwg) into .agents/skills/artifact-metadata in your project. Codex loads it when a task matches its description.
Can I use Artifact Metadata in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jmagly/aiwg --skill artifact-metadata -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/artifact-metadata, .gemini/skills/artifact-metadata, .github/skills/artifact-metadata and .opencode/skills/artifact-metadata in your project.
What does Artifact Metadata need to run?
Going by SKILL.md and its folder, Artifact Metadata needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.
Does Artifact Metadata access the network?
SKILL.md names 1 domain. In commands or code: json-schema.org; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Artifact Metadata safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Artifact Metadata use?
Artifact Metadata is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Artifact Metadata use?
About 1.9k tokens (SKILL.md is roughly 7.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Artifact Metadata?
Skills that share tags, products or a category with Artifact Metadata: Extracting Browser History Artifacts (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Artifacts Builder (nexu-io/open-design, 100k stars), Web Artifacts Builder (anthropics/skills, 180k stars) and Web Artifacts Builder (nexu-io/open-design, 100k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Artifact Metadata?
jmagly (a GitHub user) maintains it in jmagly/aiwg, which has 220 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 8, 2026.
Source: jmagly/aiwg on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.