Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add OutSystems/outsystems-mcp/plugin install outsystemsWrote 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/outsystems/outsystems-mcp/outsystems-dependency-impact)<a href="https://agentmods.dev/skills/outsystems/outsystems-mcp/outsystems-dependency-impact"><img src="https://agentmods.dev/badge/skills/outsystems/outsystems-mcp/outsystems-dependency-impact/github.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/outsystems/outsystems-mcp/outsystems-dependency-impact"><img src="https://agentmods.dev/badge/skills/outsystems/outsystems-mcp/outsystems-dependency-impact.svg" alt="Reviewed on agentmods" width="80" 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.00185 | $0.06770 |
| Opus 5.5 | $0.00074 | $0.02708 |
| Sonnet 5.5 | $0.00037 | $0.01354 |
| Haiku 4.5 | $0.00018 | $0.00677 |
Grade A, and why
outsystems-dependency-impact 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 7d 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 — 526 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Beta Feature. This skill is a Beta Feature: a non-final OutSystems capability provided to collect customer feedback. It can change significantly, including through breaking changes, or be discontinued. The first time you use this skill in a conversation, tell the user it's a Beta Feature and share https://www.outsystems.com/legal/beta-features-agreement.
OutSystems Dependency Impact
Produces a single-file HTML reverse-dependency explorer (it loads only its
fonts from a public CDN). Pick a
library, agent or connection — the page shows every asset that would
break if it were removed, in which environments, at which deployed
revision, and with what severity (Error / Warning).
The data comes from the platform's deletion-impact analysis:
deploy_impact {key, delete: true}, polled with deploy_impact_status.
It is an analysis only — nothing is deleted, and the MCP server calls no
delete endpoint for it. For "if I publish library X, who breaks?" it
lists everyone who depends on X; that is the most a pre-publish check can
give for a library (the deployment variant of the analysis does not work
for library types).
Cost and time (estimates)
| Question | Calls | Wall time | Tokens |
|---|---|---|---|
| One named target | 1 launch + 1–3 polls | seconds | ~3–5K, plus ~0.1–0.15K per dependent |
| Whole-tenant map, N targets | N launches + N+ polls, 10 per message | ~0.5–1 min per 10 targets | ~0.5K × N, plus ~0.1–0.15K per dependent |
These are estimates, not end-to-end measurements. Measured live: a launch returns in about a second, and finished reports came back for every analysis polled; a heavily used UI library had 74 dependents in a report of about 37 KB (roughly 9K tokens). The whole-tenant map is still one analysis per target, so for a large tenant it is not cheap — prefer the one-target path whenever the user names a target.
Prerequisites
- The OutSystems MCP server is connected and signed in. This skill reads
the tools named below; tool names here are the server's own, and your
harness may show them with a prefix (in Claude Code,
mcp__plugin_outsystems_outsystems__deploy_impactfordeploy_impact). - A shell with
python3(3.8 or later, standard library only). The script reads the saved analysis results from disk and writes the HTML; it never calls the server and holds no sign-in of its own. <skill-folder>below is this skill's own folder: the one holding this file (in the OutSystems plugin,skills/outsystems-dependency-impact/), so<skill-folder>/scripts/build.pyis the script next to it. Values in angle brackets are placeholders you substitute; quote every path, since a home folder can contain spaces.- Run every
build.pycommand on its own and exactly as this file writes it: the skill's permissions matchpython3 "<skill-folder>/scripts/build.py" ...and nothing else, so an added redirect (2>&1), pipe or chained command (;,&&) makes the harness stop and ask the user. - No shell available? Stop and tell the user this skill needs one (for example Claude Code, not Claude Desktop's Chat tab); don't try to build the page by hand.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 526 lines · 185 tokens per session scan A 375983ec1a9e
outsystems-dependency-impact is a skill published in the GitHub repository OutSystems/outsystems-mcp (40 stars, last pushed today), licensed MIT. It adds 185 tokens to every session and 6,770 once invoked, about $0.0007 per session on Opus 5.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-10-07.
Other skills, from other repositories
security-conductor
Operating procedure for the kirocrew-security-conductor agent. Use when a security conductor session is seeded, inspected or debugged. Run vulnerability discovery on one target as a supervised fleet — one auditor per attack surface, an independent verifier per finding, two human gates.
artifact-deploy
One-click deploy a user's pre-built app/artifact into their OWN AWS account and get a global public HTTPS link (Vercel-like), with a default TTL and promote-to-persistent. Use when the user says "deploy this", "ship this demo", "give me a public link", "share this externally", or "deploy to AWS".
widgets
Render rich HTML inline via tags with theme-aware styling. Load when emitting an mcwidget so the iframe inherits the dashboard theme instead of clashing with light / dark / custom palettes.
explain-for
Explain a topic, code, error or design decision for one named audience (a 5-year-old, a manager, a designer, a grad student, a parent). Resolves who it is for, pins the ground truth first, then tunes vocabulary, analogy, tone and depth to that audience. Use when an audience is named.
web-verify
Use after a user-visible UI edit to verify your OWN change on an isolated loopback server. Capture, read and show real screenshots. Backends: playwright-cli (live Browser panel), agent-browser (annotated frames, pixel diff, a11y), or scripted Playwright. Not web-preview or external-page web-browse.
learn-from-sage
Detection-gap (miss) analysis for Code Review Sage. Learn from shipped fixes, acted-on human comments, and design outcomes to close reviewer blind spots. Inline during review stages a candidate; a human triggers a one-shot AI consolidation into the live ruleset.