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/spree/agent-skills/spree-adminnpx skills add spree/agent-skills --skill spree-admingit clone --depth 1 https://github.com/spree/agent-skillsWrote 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/spree/agent-skills/spree-admin)<a href="https://agentmods.dev/skills/spree/agent-skills/spree-admin"><img src="https://agentmods.dev/badge/skills/spree/agent-skills/spree-admin.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.00097 | $0.03871 |
| Opus 5 | $0.00048 | $0.01936 |
| Sonnet 5 | $0.00019 | $0.00774 |
| Haiku 4.5 | $0.00010 | $0.00387 |
Grade A, and why
spree-admin 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 4d 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 — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spree Legacy Rails Admin (spree_admin)
Commands below use the Spree CLI form (
spree …, Docker). On a classic Rails app without the CLI (typical pre-5.4), use the native mapping in thespree-projectskill —bin/rails/bundle exec rakefrom the app root, paths without thebackend/prefix.
The admin is a Rails engine — server-rendered ERB views, Stimulus + Turbo for interactivity, Tailwind for styling. (Spree 6.0 will introduce a new React-based admin; on Spree 5.x, spree_admin is the admin.)
Project layout
The Rails admin lives in the spree_admin gem, mounted at /admin. View it as a normal Rails app:
spree_admin gem
├── app/
│ ├── controllers/spree/admin/ # admin controllers
│ ├── views/spree/admin/<resource>/ # ERB views per resource
│ ├── helpers/spree/admin/ # view helpers
│ ├── presenters/spree/admin/ # presenter pattern for complex views
│ ├── javascript/spree/admin/ # Stimulus controllers, importmap-managed
│ └── models/spree/admin/navigation* # nav + nav builder
└── lib/generators/spree/admin/
├── install/ # bin/rails g spree:admin:install
└── scaffold/ # bin/rails g spree:admin:scaffold
In a host app (backend/), you customize by overriding files at the same paths under backend/app/. Rails view path resolution prefers the host app's files over the gem's.
Adding a new admin resource (the one-command path)
Spree ships an admin scaffold generator that produces the full CRUD admin for any model. After the model + migration exist (use spree:api_resource or spree:model):
spree rails g spree:admin:scaffold Spree::Brand
This emits:
| File | Purpose |
|---|---|
backend/app/controllers/spree/admin/brands_controller.rb |
Controller inheriting Spree::Admin::ResourceController |
backend/app/views/spree/admin/brands/index.html.erb |
Listing page (renders render_table @collection, :brands; columns come from the table registry) |
backend/app/views/spree/admin/brands/new.html.erb |
Create form page |
backend/app/views/spree/admin/brands/edit.html.erb |
Edit form page |
backend/app/views/spree/admin/brands/_form.html.erb |
Shared form partial |
backend/config/initializers/spree_admin_brands_table.rb |
Table column registration |
backend/config/initializers/spree_admin_brands_navigation.rb |
Sidebar nav registration |
backend/config/routes.rb |
namespace :admin { resources :brands } injected into the add_routes block |
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.
- 4d ago First seen · 279 lines · 97 tokens per session scan A bfe23abcdd74
spree-admin is a skill published in the GitHub repository spree/agent-skills (4 stars, last pushed 2mo ago), licensed MIT. It adds 97 tokens to every session and 3,871 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-31.
Other skills, from other repositories
nemoclaw-contributor-implement-issue
Implement an accepted NemoClaw GitHub issue in the current checkout. Use when a user asks to pick up an issue for implementation, implement or fix a named issue, or add the issue's tests. Confirm accepted scope, deliver the smallest independently valuable capability slice, and record validation and remaining gates…
amazon-reviews-api-skill
This skill helps users automatically extract Amazon product reviews via the Amazon Reviews API. Agent should proactively apply this skill when users express needs like getting reviews for Amazon product with ASIN B07TS6R1SF, analyzing customer feedback for a specific Amazon item, getting ratings and comments for a…
amazon-competitor-analyzer
Scrapes Amazon product data from ASINs using browseract.com automation API and performs surgical competitive analysis. Compares specifications, pricing, review quality, and visual strategies to identify competitor moats and vulnerabilities.
shopify-functions
Shopify Functions allow developers to customize the backend logic that powers parts of Shopify. Available APIs: Discount, Cart and Checkout Validation, Cart Transform, Pickup Point Delivery Option Generator, Delivery Customization, Fulfillment Constraints, Local Pickup Delivery Option Generator, Order Routing Location…
food-order
Reorder previous Foodora orders, preview cart contents, and track delivery ETA/status with ordercli. Use when the user wants to reorder food, check delivery status, or browse recent Foodora order history. Never confirm an order without explicit user approval.
asc-subscription-localization
Bulk-localize subscription, subscription-group, and in-app purchase display names across App Store locales using asc, including API 4.4.1 version-scoped v2 resources. Use when filling or updating subscription/IAP names and descriptions without App Store Connect UI work.