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/andersonlemesc/oryntra/fortify-developmentnpx skills add andersonlemesc/Oryntra --skill fortify-developmentgit clone --depth 1 https://github.com/andersonlemesc/OryntraWrote 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/andersonlemesc/oryntra/fortify-development)<a href="https://agentmods.dev/skills/andersonlemesc/oryntra/fortify-development"><img src="https://agentmods.dev/badge/skills/andersonlemesc/oryntra/fortify-development.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.00199 | $0.01621 |
| Opus 5 | $0.00100 | $0.00811 |
| Sonnet 5 | $0.00040 | $0.00324 |
| Haiku 4.5 | $0.00020 | $0.00162 |
Grade A, and why
fortify-development 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.
This is a copy
100% identical to fortify-development — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Laravel Fortify Development
Fortify is a headless authentication backend that provides authentication routes and controllers for Laravel applications.
Documentation
Use search-docs for detailed Laravel Fortify patterns and documentation.
Usage
- Routes: Use
list-routeswithonly_vendor: trueandaction: "Fortify"to see all registered endpoints - Actions: Check
app/Actions/Fortify/for customizable business logic (user creation, password validation, etc.) - Config: See
config/fortify.phpfor all options including features, guards, rate limiters, and username field - Contracts: Look in
Laravel\Fortify\Contracts\for overridable response classes (LoginResponse,LogoutResponse, etc.) - Views: All view callbacks are set in
FortifyServiceProvider::boot()usingFortify::loginView(),Fortify::registerView(), etc.
Available Features
Enable in config/fortify.php features array:
Features::registration()- User registrationFeatures::resetPasswords()- Password reset via emailFeatures::emailVerification()- Requires User to implementMustVerifyEmailFeatures::updateProfileInformation()- Profile updatesFeatures::updatePasswords()- Password changesFeatures::twoFactorAuthentication()- 2FA with QR codes and recovery codesFeatures::passkeys()- Passwordless authentication with WebAuthn passkeys
Use
search-docsfor feature configuration options and customization patterns.
Setup Workflows
Two-Factor Authentication Setup
- [ ] Add TwoFactorAuthenticatable trait to User model
- [ ] Enable feature in config/fortify.php
- [ ] If the `*_add_two_factor_columns_to_users_table.php` migration is missing, publish via `php artisan vendor:publish --tag=fortify-migrations` and migrate
- [ ] Set up view callbacks in FortifyServiceProvider
- [ ] Create 2FA management UI
- [ ] Test QR code and recovery codes
Use
search-docsfor TOTP implementation and recovery code handling patterns.
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 · 151 lines · 199 tokens per session scan A 3af9cd6d8145
fortify-development is a skill published in the GitHub repository andersonlemesc/Oryntra (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 199 tokens to every session and 1,621 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to fortify-development, differing in 1 line, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…