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/aropan/clist/add-management-commandnpx skills add aropan/clist --skill add-management-commandgit clone --depth 1 https://github.com/aropan/clistWrote 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/aropan/clist/add-management-command)<a href="https://agentmods.dev/skills/aropan/clist/add-management-command"><img src="https://agentmods.dev/badge/skills/aropan/clist/add-management-command.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 | $0.00106 | $0.02015 |
| Opus 5 | $0.00053 | $0.01007 |
| Sonnet 5 | $0.00021 | $0.00403 |
| Haiku 4.5 | $0.00011 | $0.00201 |
Grade A, and why
add-management-command 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 5d 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add a CLIST management command (+ cron/Healthchecks monitor)
Management commands live in src/ranking/management/commands/ (16 existing).
They back the cron schedule (config/cron) and the RQ workers. Always read
2–3 similar ones first — set_account_rank.py, set_country_fields.py, and
anonymize_accounts.py are the cleanest references.
The CLIST skeleton (copy this)
#!/usr/bin/env python3
from logging import getLogger
from django.core.management.base import BaseCommand
from django.db.models import Q
from django.utils import timezone
from django_print_sql import print_sql_decorator
from tqdm import tqdm
from clist.models import Resource
from ranking.models import Account
from utils.attrdict import AttrDict
class Command(BaseCommand):
help = 'One-line description'
def __init__(self, *args, **kwargs):
super().__init__(*args, **kwargs)
self.logger = getLogger('ranking.<command_name>')
def add_arguments(self, parser):
parser.add_argument('-r', '--resources', metavar='HOST', nargs='*', help='resources hosts')
parser.add_argument('-n', '--limit', type=int, help='number of items to process')
parser.add_argument('--verbose', action='store_true', help='verbose output')
@print_sql_decorator(count_only=True)
def handle(self, *args, **options):
self.stdout.write(str(options)) # ALWAYS first line
args = AttrDict(options)
resources = Resource.available_for_update_objects.all()
if args.resources:
resources = Resource.get(args.resources, queryset=resources) # host + short_host aware
if args.limit:
resources = resources[:args.limit]
for resource in tqdm(resources, total=len(resources), desc='resources'):
... work ...
Why each piece
| Piece | Why |
|---|---|
self.logger = getLogger('ranking.<name>') in __init__ |
Lets workers/cron capture per-command logs. Naming: <app>.<command> is dominant; use <app>.<cluster>.<name> (e.g. ranking.parse.statistic) for a related subgroup. |
self.stdout.write(str(options)) as the first line of handle |
Echoes parsed flags into the run log — essential for EventLog forensics and cron debugging. Universally present. |
args = AttrDict(options) right after |
AttrDict (utils/attrdict.py) makes every key an attribute — args.resources not options['resources']. Pervasive. |
@print_sql_decorator(count_only=True) on handle |
Counts DB queries without dumping SQL. Optional but very common. |
.save(..., update_fields=[...]) everywhere |
Never call .save() without update_fields in a command — avoids clobbering concurrent updates and shrinks the query. |
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.
- 5d ago First seen · 186 lines · 106 tokens per session scan A f1e87e2bc02b
add-management-command is a skill published in the GitHub repository aropan/clist (440 stars, last pushed 19d ago), licensed Apache-2.0. It adds 106 tokens to every session and 2,015 once invoked, about $0.0005 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.
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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…