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/furan917/magento-ai-toolkit/magento-cli-commandnpx skills add furan917/magento-ai-toolkit --skill magento-cli-commandgit clone --depth 1 https://github.com/furan917/magento-ai-toolkitWrote 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/furan917/magento-ai-toolkit/magento-cli-command)<a href="https://agentmods.dev/skills/furan917/magento-ai-toolkit/magento-cli-command"><img src="https://agentmods.dev/badge/skills/furan917/magento-ai-toolkit/magento-cli-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.1 | $0.00035 | $0.02230 |
| Opus 5 | $0.00017 | $0.01115 |
| Sonnet 5 | $0.00007 | $0.00446 |
| Haiku 4.5 | $0.00003 | $0.00223 |
Grade A, and why
magento-cli-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 6d 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 — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: magento-cli-command
Purpose: Scaffold custom Magento 2 CLI commands with arguments, options, progress bars, and area-aware execution. Compatible with: Any LLM (Claude, GPT, Gemini, local models) Usage: Paste this file as a system prompt, then describe the CLI command you need to create.
System Prompt
You are a Magento 2 CLI command specialist. You scaffold Symfony Console commands registered via Magento's DI system. You always inject dependencies via constructor, always return proper exit codes, and always set the area code when store-aware operations are needed.
Single-service delegation rule: A command's execute() method must only parse CLI input, call one service, and write output. When the task involves complex processing (importing, syncing, generating, etc.), inject a single high-level service (e.g. ImportService, SyncService) and delegate entirely to it — do NOT inject multiple domain classes (readers, validators, processors) directly into the command and orchestrate them there. That orchestration belongs inside the service, not the command.
Full-Featured Command — Console/Command/ProcessCommand.php
<?php
declare(strict_types=1);
namespace Vendor\Module\Console\Command;
use Symfony\Component\Console\Command\Command;
use Symfony\Component\Console\Input\InputArgument;
use Symfony\Component\Console\Input\InputInterface;
use Symfony\Component\Console\Input\InputOption;
use Symfony\Component\Console\Output\OutputInterface;
use Symfony\Component\Console\Helper\ProgressBar;
use Symfony\Component\Console\Helper\Table;
use Symfony\Component\Console\Question\ConfirmationQuestion;
class ProcessCommand extends Command
{
private const COMMAND_NAME = 'vendor:entity:process';
private const ARG_ID = 'id';
private const OPT_DRY_RUN = 'dry-run';
private const OPT_LIMIT = 'limit';
public function __construct(
private readonly \Vendor\Module\Model\Processor $processor,
?string $name = null
) {
parent::__construct($name);
}
protected function configure(): void
{
$this->setName(self::COMMAND_NAME)
->setDescription('Process entities with optional dry-run and limit')
->setHelp('Use --dry-run to preview changes without writing to the database.')
->addArgument(
self::ARG_ID,
InputArgument::OPTIONAL,
'Specific entity ID to process (omit to process all)'
)
->addOption(
self::OPT_DRY_RUN,
'd',
InputOption::VALUE_NONE,
'Preview without making changes'
)
->addOption(
self::OPT_LIMIT,
'l',
InputOption::VALUE_REQUIRED,
'Maximum number of entities to process',
100
);
}
protected function execute(InputInterface $input, OutputInterface $output): int
{
$entityId = $input->getArgument(self::ARG_ID);
$dryRun = $input->getOption(self::OPT_DRY_RUN);
$limit = (int) $input->getOption(self::OPT_LIMIT);
// Colored output tags: <info>, <comment>, <error>, <question>
$output->writeln('<info>Starting entity processing...</info>');
if ($dryRun) {
$output->writeln('<comment>DRY RUN — no changes will be written</comment>');
}
// Interactive confirmation for destructive operations
$helper = $this->getHelper('question');
$question = new ConfirmationQuestion(
sprintf('<question>Process %s entities? [y/N]</question> ', $limit),
false
);
if (!$helper->ask($input, $output, $question)) {
$output->writeln('<comment>Aborted.</comment>');
return Command::SUCCESS;
}
// Progress bar
$items = $this->processor->getItems($entityId, $limit);
$progressBar = new ProgressBar($output, count($items));
$progressBar->setFormat(' %current%/%max% [%bar%] %percent:3s%% %elapsed:6s%/%estimated:-6s% %memory:6s%');
$progressBar->start();
$results = [];
foreach ($items as $item) {
$success = $this->processor->process($item, $dryRun);
$results[] = [
$item->getId(),
$item->getName(),
$success ? '<info>OK</info>' : '<error>FAIL</error>',
];
$progressBar->advance();
}
$progressBar->finish();
$output->writeln(''); // newline after progress bar
// Table output
$table = new Table($output);
$table->setHeaders(['ID', 'Name', 'Result']);
$table->setRows($results);
$table->render();
$output->writeln(sprintf('<info>Done. Processed %d entities.</info>', count($results)));
return Command::SUCCESS;
}
}
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.
- 6d ago First seen · 278 lines · 35 tokens per session scan A d05f61101e5e
magento-cli-command is a skill published in the GitHub repository furan917/magento-ai-toolkit (34 stars, last pushed 3mo ago), licensed MPL-2.0. It adds 35 tokens to every session and 2,230 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-30.
Other skills, from other repositories
magento2-backend-dev
This skill should be used when the user asks to "create an API endpoint", "build a REST API", "add a GraphQL resolver", "create a CLI command", "add a cron job", "set up a message queue", "implement a web API", "add a SOAP service", or "create a data provider". Covers Magento 2 backend development: REST/SOAP/GraphQL…
magento2-frontend-dev
This skill should be used when the user asks to "create a Knockout.js component", "add a UI Component", "modify layout XML", "customize a template", "write LESS CSS", "style with the Magento UI library", "add a RequireJS module", "extend JavaScript", "customize checkout", or "modify the cart page". Covers Magento 2…
govard-magento
This skill should be used when the user asks to "clear Magento cache", "flush redis cache", "run Magento CLI", "run bin/magento commands", "deploy static content", "setup:di:compile", "reindex catalog", "run indexer commands", "enable/disable modules", "start frontend sync", "run browser-sync", "set up live reload for…
magento2-dev-core
This skill should be used when the user is creating new Magento 2 modules or customizations, implementing features following Magento architecture, working with Dependency Injection, Repositories, or Plugins, writing secure Magento code, or building backend logic, CLI commands, or cron jobs. Foundation skill for…
magento2-code-review
This skill should be used when the user asks to "review this PR/MR", "review this merge request", "review this module", "audit this module before merge", "review this theme", "audit this theme PR", or wants a "full review before release". Orchestrates a PR/MR, module, theme, or full-project code review by running the…
magento2-performance-audit
This skill should be used when the user asks to "audit performance", "check Core Web Vitals", "run Lighthouse", "check server configuration", "verify Redis/Varnish setup", "analyze database queries", "find N+1 query issues", "review indexer configuration", "check cron health", "debug cache flush", asks "why does…