Eventyay is an open-source platform for managing events, including ticket sales and registration, speaker submissions, session schedules, videos, check-ins, badges, exhibitions, and organiser administration. Event organisers use it to run both in-person and online event workflows.
Borrowing it
Nothing to install: this file belongs to fossasia/eventyay. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fossasia/eventyay/dev/.agents/skills/connect-required-verification-information/SKILL.mdgit clone --depth 1 https://github.com/fossasia/eventyayWrote 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/fossasia/eventyay/connect-required-verification-information)<a href="https://agentmods.dev/skills/fossasia/eventyay/connect-required-verification-information"><img src="https://agentmods.dev/badge/skills/fossasia/eventyay/connect-required-verification-information/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/fossasia/eventyay/connect-required-verification-information"><img src="https://agentmods.dev/badge/skills/fossasia/eventyay/connect-required-verification-information.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.00080 | $0.06399 |
| Opus 5.5 | $0.00032 | $0.02560 |
| Sonnet 5.5 | $0.00016 | $0.01280 |
| Haiku 4.5 | $0.00008 | $0.00640 |
Grade A, and why
connect-required-verification-information scanned grade A with 1 finding 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 21d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
### curl examples This is a copy
84% identical to connect-required-verification-information — 18 lines 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 — 413 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instructions
The human-accessible version of this documentation allows the user to select connected account fields and regions using a form, and then makes API requests to fetch and display the requirements a connected account with the selected configuration and region must provide. Follow these instructions to fetch the same information.
Interaction contract
Terminology used in this document:
field: a setup input such asplatformCountry,accountCountry, orcapabilitiesoption: a presented selectable option for a fieldvalue: the option the user selects, or the free-response value the user provides for a field
Every time you ask the user to provide a value for a field:
- use a multiple-choice question; never stop at a plain free-form prompt or wait for raw chat input
- if you need free user input, instruct the user to use the question’s free-response field
- for long option lists, explicitly say that any value from the full validated list is still accepted through the free-response field
- if the user already provided a valid answer in an earlier message, use that instead of asking again
Hard rules
You must follow these rules:
- Ask for a field only after all of its prerequisite fields are satisfied.
- Collect setup fields progressively as the flow advances.
- Ask for one field at a time, or one group of fields only when they are dependency-free at that point in the flow.
- For example, ask for
platformCountryandaccountCountryseparately: the platform country determines which account countries are valid, so asking both together can produce invalid combinations. But you may ask fordashboardType,tosType, andlegalEntityTypetogether in one group because their valid options are already known from the same response.
- For example, ask for
- If there is ever a conflict between the user’s request and the validated setup, inform the user of the conflict and ask them to revise their setup choices using the Interaction contract. Keep the validated setup aligned with what the user requested without silently dropping the conflict.
- Follow the Interaction contract for every user question.
- When the number of available options exceeds four, always print the full validated reference list before asking the multiple-choice question so the user can see the full option space.
- When printing countries, always print the full country name followed by its code in parentheses, for example,
Germany (DE). - In the multiple-choice question, include a small set of suggested options so the user can move forward with immediate clarity. The reference list above remains the authoritative full set.
- Leave the descriptions for the country suggested options blank.
- When printing countries, always print the full country name followed by its code in parentheses, for example,
- For any field with four or fewer valid options, show every valid option directly in the multiple-choice question. Do not print a separate reference list first.
- Every list of selectable options shown to the user must be pre-validated against all currently known constraints before you display it.
- Never display an option as selectable if you already know it will be removed, rejected, or auto-adjusted later in the flow.
- Present options that stay valid through the current flow.
- Ask about
capabilitiesafterplatformCountry,accountCountry, and the downstream validity constraints for that setup are resolved. - Only ask about
orrProgramwhen it is present in the publicprogramsreturned for the validated setup. - If the
businessStructuremap for the chosenlegalEntityTypeis empty or contains exactly one keynil, skipbusinessStructure. Otherwise, ask forbusinessStructureand always allow anoneoption or leave unselected as a suggested option in the multiple-choice question. - If the user decides to change an earlier choice like
platformCountry, you must invalidate and re-check all downstream fields before continuing. - Keep the dependency chain implicit. Share the information the user needs to make progress and keep the experience simple.
- Use external-facing language when talking to the user. See below to translate the internal API terminology.
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.
- 21d ago First seen · 413 lines · 80 tokens per session scan A 9945d4ad0c46
connect-required-verification-information is a skill published in the GitHub repository fossasia/eventyay (1,710 stars, last pushed today), licensed Apache-2.0. It adds 80 tokens to every session and 6,399 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). It is 84% identical to connect-required-verification-information, differing in 18 lines, and is treated as a copy.
Other skills, from other repositories
expense-review-policy
Review invoices and contracts against accounts-payable policy before human approval.
audit-support
Support SOX 404 compliance with control testing methodology, sample selection, and documentation standards. Use when generating testing workpapers, selecting audit samples, classifying control deficiencies, or preparing for internal or external audits.
kyc-doc-parse
Parse an investor or client onboarding packet into structured KYC fields — identity, ownership, control, source of funds, and document inventory. Use as the first step of KYC screening; output feeds the rules engine.
subcontractor-payment-tracker
Track subcontractor payments, lien waivers, and compliance. Manage payment schedules and documentation.
fiscaliste
Fiscaliste IA pour la fiscalité personnelle des particuliers français : optimisation et déclaration de l'impôt sur le revenu, IFI, revenus du capital, revenus fonciers, equity salarial, crypto-actifs et PER. Couvre le calcul de l'IR (barème, quotient familial, décote, PAS, CEHR, revenus exceptionnels), la déclaration…
china-process-letter
A guide for writing process letters and bid instructions for Chinese A-share mergers and acquisitions. These documents tell potential buyers how to submit an initial offer, final bid, attend management meetings, and use a due-diligence data room.