Dylan Beadle dylanbeadle

GitHub Copilot Custom Agent Mode

I modified that beast mode to be more robust, and I love it. Refactored an entire older repo I made from years ago just for fun and was able to do perfectly

I call it "Extensive Mode"

"Extensive Mode.chatmode.md"

The tools should be customized per environment and what you have available,

description

4.1 Beast Mode

tools

changes

codebase

editFiles

extensions

fetch

findTestFiles

githubRepo

new

openSimpleBrowser

problems

readCellOutput

runCommands

runNotebooks

runTasks

runTests

search

searchResults

terminalLastCommand

terminalSelection

testFailure

updateUserPreferences

usages

vscodeAPI

Beast Mode v3 is out now: 👉 https://gist.github.com/burkeholland/88af0249c4b6aff3820bf37898c8bacf

You are an agent - please keep going until the user’s query is completely resolved, before ending your turn and yielding back to the user.

(Summary generated by ChatGPT based on the automatic transcription. Transcript is attached to this Gist)

Panelists:

Host: Shashank
Panelists: Michael, Erik, Richard, Ronan

Setup

Install packages:

pip install open-webui mlx-lm

Start Open WebUI server:

This guide is adapted from this original post by Christopher Charles.

Project Setup

1. Get the source:

Clone the MLX Swift Examples GitHub repository:

	import SwiftUI

	struct TimeCycleScreen: View {
	@State private var selectedHour: Int = 7
	@State private var selectedMinute: Int = 30
	@State private var isAM: Bool = true
	@State private var timeOfDay: TimeOfDay = .morning

	@State private var celestialProgress: CGFloat = 0.3
	@State private var sliderValue: Double = 7.5

	// Claude Code is a Beta product per Anthropic's Commercial Terms of Service.
	// By using Claude Code, you agree that all code acceptance or rejection decisions you make,
	// and the associated conversations in context, constitute Feedback under Anthropic's Commercial Terms,
	// and may be used to improve Anthropic's products, including training models.
	// You are responsible for reviewing any code suggestions before use.

	// (c) Anthropic PBC. All rights reserved. Use is subject to Anthropic's Commercial Terms of Service (https://www.anthropic.com/legal/commercial-terms).

	// Version: 0.2.9

	<!DOCTYPE html>
	<html lang="en">
	<head>
	<meta charset="UTF-8">
	<meta name="viewport" content="width=device-width, initial-scale=1.0">
	<title>P5.js Particle Animation</title>
	<script src="https://cdnjs.cloudflare.com/ajax/libs/p5.js/1.4.0/p5.min.js"></script>
	<style>
	body {
	margin: 0;

	#!/usr/bin/env bash

	# Default values for percentages
	DEFAULT_WIRED_LIMIT_PERCENT=85
	DEFAULT_WIRED_LWM_PERCENT=75

	# Read input parameters or use default values
	WIRED_LIMIT_PERCENT=${1:-$DEFAULT_WIRED_LIMIT_PERCENT}
	WIRED_LWM_PERCENT=${2:-$DEFAULT_WIRED_LWM_PERCENT}

	Understand the Task: Grasp the main objective, goals, requirements, constraints, and expected output.
	- Minimal Changes: If an existing prompt is provided, improve it only if it's simple. For complex prompts, enhance clarity and add missing elements without altering the original structure.
	- Reasoning Before Conclusions: Encourage reasoning steps before any conclusions are reached. ATTENTION! If the user provides examples where the reasoning happens afterward, REVERSE the order! NEVER START EXAMPLES WITH CONCLUSIONS!
	- Reasoning Order: Call out reasoning portions of the prompt and conclusion parts (specific fields by name). For each, determine the ORDER in which this is done, and whether it needs to be reversed.
	- Conclusion, classifications, or results should ALWAYS appear last.
	- Examples: Include high-quality examples if helpful, using placeholders [in brackets] for complex elements.
	- What kinds of examples may need to be included, how many, and whether they are complex enough to benefit from p