eventyay: Instructions file for GitHub Copilot

.github/instructions/js.instructions.md

eventyay js.instructions.md is an instructions file for GitHub Copilot from fossasia/eventyay. It costs 601 tokens per session, scanned A, original, Apache-2.0.

JavaScript and Vue development rules covering older scripts without a build step and modern Vue 3 applications bundled for deployment.

In plain words
What is it for?
Use them when writing or updating JavaScript or Vue code, especially scripts that make network requests or run under a content security policy.
Why use it?
They prevent patterns the project disallows, such as jQuery, inline scripts, and unclear handling of asynchronous errors.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is fossasia/eventyay's own configuration. It tells GitHub Copilot how to work on eventyay itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything eventyay configures →

About the project

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.

fossasia/eventyay · 1,710 stars · on GitHub · eventyay.com

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/fossasia/eventyay/dev/.github/instructions/js.instructions.md
Clone the repo
git clone --depth 1 https://github.com/fossasia/eventyay

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for eventyay js.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/fossasia/eventyay/js/github.svg)](https://agentmods.dev/instructions/fossasia/eventyay/js)
Your own site
<a href="https://agentmods.dev/instructions/fossasia/eventyay/js"><img src="https://agentmods.dev/badge/instructions/fossasia/eventyay/js/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.

agentmods 80×15 button for eventyay js.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/fossasia/eventyay/js"><img src="https://agentmods.dev/badge/instructions/fossasia/eventyay/js.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 601 This file is loaded in full into every session.
When invoked 601 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00601 $0.00601
Opus 5.5 $0.00240 $0.00240
Sonnet 5.5 $0.00120 $0.00120
Haiku 4.5 $0.00060 $0.00060

Measured 1mo ago against content hash fb23815541b3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

eventyay js.instructions.md 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 1mo 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.

.github/instructions/js.instructions.md · 74 lines

How it starts

The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Development Standards

Modernization

  • Do not use jQuery
  • Use ES modules, not IIFEs.
  • Implement as external scripts; do not use inline scripts because they are blocked by CSP.

Error handling

  • Always log errors with contextual information. You may skip this when letting the error bubble up to be handled by a higher-level component or function.

  • Use try/catch blocks in async functions to handle exceptions gracefully. You may skip this when letting the error bubble up to be handled by a higher-level component or function, but you must add a comment documenting that the function may throw errors. For example:

    /**
    * @throws {HTTPError} when the network request fails
    */
    async function fetchData() {
      const response = await ky.get('/some-endpoint')
      return response.json()
    }
    
  • When working with a library that provides its own error types (such as ky with HTTPError), do not replace this specific error type with a generic one. For example, do not do this:

    try {
      await ky.get('/some-endpoint')
    } catch (error) {
      throw new Error('Failed to fetch data') // Bad: replacing HTTPError with generic Error
    }
    

    Instead, let the error bubble up (with a comment), or do this:

    try {
      await ky.get('/some-endpoint')
    } catch (error) {
      if (error instanceof HTTPError) {
        // Handle HTTPError specifically
        throw error // Re-throw the original error
      }
      throw new Error('An unexpected error occurred') // Handle other errors
    }
    
  • Do not create empty catch blocks.

DOM access

  • Be careful when using .closest(selector) because it makes the page fragile to DOM changes. Choose a selector carefully so that the code does not break when the DOM changes.

Comments

  • Do not add a comment when the code is already obvious and the comment is almost the same as the code.

Frontend Code Locations

Path Purpose
app/eventyay/static/ Static assets served by Django (CSS, legacy JS)
app/eventyay/webapp/ Modern JS applications (Vue 3, built with a bundler)

Read the full file on GitHub · 74 lines

Changes

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.

  1. 1mo ago First seen · 74 lines · 601 tokens per session scan A fb23815541b3

Subscribe to this mod's changes

eventyay js.instructions.md is an instructions file published in the GitHub repository fossasia/eventyay (1,710 stars, last pushed today), licensed Apache-2.0. It adds 601 tokens to every session, about $0.0024 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-08-30.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,649 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,257 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,159 tokens