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 skills add VersoXBT/claude-initial-setup --skill django-admin-customizationgit clone --depth 1 https://github.com/VersoXBT/claude-initial-setupWrote 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/versoxbt/claude-initial-setup/django-admin-customization)<a href="https://agentmods.dev/skills/versoxbt/claude-initial-setup/django-admin-customization"><img src="https://agentmods.dev/badge/skills/versoxbt/claude-initial-setup/django-admin-customization.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/versoxbt/claude-initial-setup/django-admin-customization"><img src="https://agentmods.dev/badge/skills/versoxbt/claude-initial-setup/django-admin-customization.svg?style=web" alt="Reviewed on agentmods" width="80" height="15"></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.1 | $0.00074 | $0.02272 |
| Opus 5 | $0.00037 | $0.01136 |
| Sonnet 5 | $0.00015 | $0.00454 |
| Haiku 4.5 | $0.00007 | $0.00227 |
Grade A, and why
django-admin-customization 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 — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Django Admin Customization
Build powerful admin interfaces with Django's built-in admin. A well-configured admin panel eliminates the need for custom CRUD dashboards and gives non-technical users a safe way to manage data.
When to Use
- User registers Django models in admin
- User needs custom list views, filters, or search
- User asks about inline editing or custom actions
- User wants to customize the admin site appearance
- User needs admin-only business operations (bulk actions, exports)
Core Patterns
ModelAdmin Configuration
from django.contrib import admin
from django.utils.html import format_html
@admin.register(Article)
class ArticleAdmin(admin.ModelAdmin):
# List view configuration
list_display = [
"title", "author_name", "category", "status",
"view_count", "colored_status", "created_at",
]
list_display_links = ["title"]
list_editable = ["status", "category"]
list_filter = ["status", "category", "created_at"]
list_per_page = 25
list_select_related = ["author", "category"]
# Search
search_fields = ["title", "body", "author__username", "author__email"]
search_help_text = "Search by title, body, or author"
# Detail view
readonly_fields = ["slug", "view_count", "created_at", "updated_at"]
prepopulated_fields = {"slug": ("title",)}
autocomplete_fields = ["author", "category"]
filter_horizontal = ["tags"]
# Fieldsets -- organize detail view into sections
fieldsets = [
(None, {
"fields": ["title", "slug", "body"],
}),
("Classification", {
"fields": ["category", "tags", "status"],
}),
("Metadata", {
"classes": ["collapse"], # Collapsible section
"fields": ["author", "view_count", "created_at", "updated_at"],
}),
]
# Date hierarchy for drill-down navigation
date_hierarchy = "created_at"
# Ordering
ordering = ["-created_at"]
@admin.display(description="Author", ordering="author__last_name")
def author_name(self, obj):
return obj.author.get_full_name()
@admin.display(description="Status")
def colored_status(self, obj):
colors = {"draft": "gray", "published": "green", "archived": "red"}
color = colors.get(obj.status, "black")
return format_html(
'<span style="color: {};">{}</span>',
color,
obj.get_status_display(),
)
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 · 313 lines · 74 tokens per session scan A 61f85f0cb2e3
django-admin-customization is a skill published in the GitHub repository VersoXBT/claude-initial-setup (4 stars, last pushed 4mo ago), licensed MIT. It adds 74 tokens to every session and 2,272 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
claudehut-workflow
Use at the start of every session and whenever beginning a coding task in a Java/Spring backend - establishes the ClaudeHut 7-phase agentic workflow, the complexity-tier routing that lets small tasks skip deliberation phases, and the laws that govern which skills and rules must fire. Injected at session start; also…
architecture-patterns
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use this skill when designing clean architecture for a new microservice, when refactoring a monolith to use bounded contexts, when implementing hexagonal or onion architecture patterns, or…
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
workflow-orchestration-patterns
Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.
ai-voice-bots
Builds production voice bots and IVR with Python STT/TTS pipelines. Use when designing telephony, streaming audio, latency budgets, or voice quality monitoring.
data-streaming
Designs streaming platforms for Kafka, Flink, CDC, and lakehouse ingestion. Use when planning event backbones, CDC pipelines, schema governance, or real-time lakehouse delivery.